Skip to content

Commit

Permalink
Update release README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
magnusbechwind authored Nov 8, 2023
1 parent f18a5a7 commit 9f82222
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions release/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ mvn versions:set -DnewVersion=$VERSION
```
where `$VERSION` is in the following format: `x.y.z`
This should set the desired version in the [pom.xml](../concordium-sdk/pom.xml).
The [pom.xml](../concordium-sdk-examples/pom.xml) in [examples](../concordium-sdk-examples) should also be changed to use this new version

1. Commit and push this new version.
1. Do a release via Github (the tagged version and the $VERSION just set should be the same)
Expand All @@ -20,12 +21,12 @@ Publishing the release invokes the `Release` workflow. The `Release` workflow ge
2. A jar-with-dependencies containing all of the above as well as all maven dependencies.
3. A jar with javadoc that can be imported to the users IDE to add documentation.

Javadoc is also uploaded to ([https://concordium.github.io/concordium-java-sdk/javadoc/concordium-sdk/apidocs/]https://concordium.github.io/concordium-java-sdk/javadoc/concordium-sdk/apidocs/)
Javadoc is also uploaded to https://concordium.github.io/concordium-java-sdk/javadoc/concordium-sdk/apidocs/

```
mvn versions:set -DnewVersion=$VERSION-SNAPSHOT
```
where `$VERSION` is the just released version.

The [pom.xml](../concordium-sdk-examples/pom.xml) in [examples](../concordium-sdk-examples) should also be changed to use this new snapshot version
1. Commit and push the `SNAPSHOT` version.

0 comments on commit 9f82222

Please sign in to comment.