Skip to content

Commit a65e647

Browse files
committed
Dangling xml node
1 parent 99d43eb commit a65e647

File tree

2 files changed

+17
-2
lines changed

2 files changed

+17
-2
lines changed

docs/release.md

+17-1
Original file line numberDiff line numberDiff line change
@@ -3,4 +3,20 @@ This is a simple checklist when performing a release.
33
1. Ensure we're up-to-date with the current spec via `./spec_finder.py --diff-output --refresh-spec`
44
2. Update `README.md` with the current spec that we're up to
55
3. Update `README.md` to keep the install instructions on the right version
6-
4. Update `<version>` in pom.xml
6+
4. Update `<version>` in pom.xml
7+
5. Run `mvn verify` to ensure it all works.
8+
6. Commit the results as the new version.
9+
10+
Then in GitHub, trigger a release.
11+
12+
1. Go to [github releases](https://github.com/open-feature/java-sdk/releases/new)
13+
2. Name a tag w/ the version you want to release (e.g. `0.1.0`)
14+
3. Click the generate release notes button and write some text about what actually changed.
15+
4. Submit
16+
5. Validate the action which builds the result happened correctly.
17+
18+
If something went wrong above, here's how you reset.
19+
1. Save the release notes you wrote.
20+
2. Delete the release.
21+
3. Delete the tag with `git push --delete origin 0.1.0` where 0.1.0 is your tag name.
22+
4.

pom.xml

-1
Original file line numberDiff line numberDiff line change
@@ -289,7 +289,6 @@
289289
<groupId>org.apache.maven.plugins</groupId>
290290
<artifactId>maven-gpg-plugin</artifactId>
291291
<version>1.5</version>
292-
</executions>
293292
</plugin>
294293
<!-- end sign -->
295294

0 commit comments

Comments
 (0)