Release 5.2.1

[johanandren]

Release Akka Persistence JDBC 5.2.1

Cutting the release

• [x] Check that open PRs and issues assigned to the milestone are reasonable
• [x] For minor or major versions, update the Change date in the LICENSE file and update the licenses url in the build.
• [x] Create a new milestone for the next version
• [x] Close the 5.2.1 milestone
• [x] 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".
• [x] Wait until main build finished after merging the latest PR
• [x] Update the draft release with the next tag version v5.2.1, title and release description. Use the Publish release button, which will create the tag.
• [x] Check that GitHub Actions release build has executed successfully (GitHub Actions will start a CI build for the new tag and publish artifacts to Maven central via Sonatype)

Check availability

• [x] Check API documentation
• [x] 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).
• [x] Check the release on Maven central

When everything is on maven central

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

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

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

• [x] Update version for Lightbend Supported Modules in private project
• [x] Update akka-dependencies bom
• [x] Update Akka Guide samples
• Close this issue

[johanandren]

Hmm, release workflow never got triggered by the tag it seems.