Release Process

Release Process

• Update dependencies
• Check all issues are closed
• Trigger release
• Update docs
• Create release notes on GitHub
• Close milestone
• Create milestone
• Announce release

Update dependencies

gradle.properties contains all dependencies. These should be up-to-date before a release is done. Align security and framework versions. Boot version is only used in samples.

Check all issues are closed

For releases to be created check that there is a milestone on GitHub and no open issues exist.

Trigger release

CI workflow handles all versions(snapshots, milestones and ga's). Which one is simply by version in gradle.properties. To create 2.0.0 or 2.0.0-RC1, update gradle.properties, commit and tag it with same version(no v prefix). Commit this version change with Release 2.0.0

When release(s) is done, revert/change version in gradle.properties to snapshot depending if release was a milestone or ga. Commit this version change with Next Development Version

$ git diff
diff --git a/gradle.properties b/gradle.properties
index e5ad866..6cf6d33 100644
--- a/gradle.properties
+++ b/gradle.properties
@@ -1,4 +1,4 @@
-version=2.0.0-SNAPSHOT
+version=2.0.0-RC1
 springBootVersion=3.0.6
 springFrameworkVersion=6.0.8
 springSecurityVersion=6.0.3


$ git add . && git commit -m "Release 2.0.0-RC1"

$ git tag 2.0.0-RC1

$ git push --tags

$ git push

$ git add . && git commit -m "Next Development Version"

$ git push

Update docs

Run deploy-docs.yml from docs-build branch

Create release notes on GitHub

Use https://github.com/spring-io/github-changelog-generator to create GitHub release body. Manually create a new GitHub release.

$ java -jar github-changelog-generator.jar --changelog.repository=spring-projects/spring-security-kerberos 2.0.0-RC1 changelog

Update version on project page

On https://spring.io/projects/spring-security-kerberos do change for versions.

Annource release

Create a blog post On slack

spring-security-kerberos-announcing 2.0.0-RC1