Skip to content

Latest commit

 

History

History
37 lines (29 loc) · 1.79 KB

File metadata and controls

37 lines (29 loc) · 1.79 KB

Releasing

In order to release the SDK on Maven Central, do the following.

  1. Change all the SDK artifacts version to X.Y.Z where it previously was X.Y.Z-SNAPSHOT: from the root of the repository invoke
    mvn versions:set -DnewVersion=$VERSION
    
    where $VERSION is in the following format: X.Y.Z. This should set the desired version in the various pom.xml files, including the pom.xml in concordium-sdk and the pom.xml in concordium-android-sdk/
  2. Update the Changelog
  3. Commit the version and changelog update
  4. Tag the commit in the following format: v.X.Y.Z
  5. Manually trigger the Release workflow for the tag. Ask for approval for the last part of the workflow
  6. Merge (squash) the release branch into main
  7. Wait for the version to appear under https://repo1.maven.org/maven2/com/concordium/sdk/
  8. Manually add Changelog entries of this version to the GitHub release, which was automatically created by the Release workflow

The released artifacts must become available here:

Javadoc

The Relase workflow also creates the branch javadoc if it does not already exist. This branch contains the generated javadoc which is visible at: https://concordium.github.io/concordium-java-sdk/javadoc/concordium-sdk/apidocs/

Useful links

Maven – Releasing the deployment