Release 5.5.0

[sebastian-alfers]

Release Akka Persistence JDBC 5.5.0

Cutting the release

• Check that open PRs and issues assigned to the milestone are reasonable
• Update the Change date and version in the LICENSE file.
• Create a new milestone for the next version
• Close the 5.5.0 milestone
• Make sure all important PRs have been merged
• Update the revision in Fossa in the Akka Group for the Akka umbrella version, e.g. 22.10. Note that the revisions for the release is udpated by Akka Group > Projects > Edit. For recent dependency updates the Fossa validation can be triggered from the GitHub actions "Dependency License Scanning".
• Wait until main build finished after merging the latest PR
• Update the draft release with the next tag version v5.5.0, title and release description. Use the Publish release button, which will create the tag.
• Check that GitHub Actions release build has executed successfully (GitHub Actions will start a CI build for the new tag and publish artifacts to https://repo.akka.io/maven)

Check availability

• Check API documentation
• Check reference documentation. Check that the reference docs were deployed and show a version warning (see section below on how to fix the version warning).
• Check the release on https://repo.akka.io/maven/com/lightbend/akka/akka-persistence-jdbc_2.13/5.5.0/akka-persistence-jdbc_2.13-5.5.0.pom

When everything is on https://repo.akka.io/maven

• Log into gustav.akka.io as akkarepo
  • If this updates the current version, run ./update-akka-persistence-jdbc-current-version.sh 5.5.0
  • otherwise check changes and commit the new version to the local git repository

    cd ~/www
    git status
    git add libraries/akka-persistence-jdbc/current libraries/akka-persistence-jdbc/5.5.0
    git add api/akka-persistence-jdbc/current api/akka-persistence-jdbc/5.5.0
    git commit -m "Akka Persistence JDBC 5.5.0"
    

Announcements

For important patch releases, and only if critical issues have been fixed:

• Send a release notification to Lightbend discuss
• Tweet using the @akkateam account (or ask someone to) about the new release
• Announce on Gitter akka/akka
• Announce internally (with links to Tweet, discuss)

For minor or major releases:

• Include noteworthy features and improvements in Akka umbrella release announcement at akka.io. Coordinate with PM and marketing.

Afterwards

• Update akka-dependencies bom and version for Akka module versions in akka-dependencies repo
• Update Akka Guide samples
• Close this issue