Release Process

Release Process steps

1. set the version to the release version with mvn versions:set and push the resulting commit to the PR
   1. if this is a Liquibase core dependency bump, align the extension version to the new version of Liquibase core, keep the -SNAPSHOT suffix
   2. else, just keep the snapshot version as is
2. set the version(s) in mkdocs.yml (without the -SNAPSHOT suffix)
3. once the PR build is ✅ , merge the PR
4. wait for the merged commit's CI to pass on main
5. edit the draft release
   1. select the tag dropdown and create a new tag (the name must start with v, e.g. v4.23.2)
   2. the title must be liquibase-neo4j-{version} (e.g. liquibase-neo4j-4.23.2)
   3. go to your local clone, pull the latest changes in main, remove the SNAPSHOT prefix from the version (don't commit it!), build (mvn clean package -DskipTests) and upload the full JAR to the release assets
   4. publish the release
6. wait for CI (a job named Release Extension to Sonatype should appear and pass)
7. ping Liquibase folks so that the release is closed in Sonatype staging
8. (once the release is published) open PR against https://github.com/neo4j/jbang-catalog/blob/main/liquibase_neo4j.java
9. (once the release is published) announce release to https://community.neo4j.com/t5/releases/liquibase-for-neo4j-releases/td-p/48843 & Neo4j Discord