Release 2.9.3

[johanandren]

Release Akka 2.9.3

Cutting the release

• Check that open PRs and issues assigned to the milestone are reasonable
• If PRs were merged after EU midnight, trigger the native-image tests and see that they are green.
• Update the version and change date in the LICENSE file.
• Update the Akka version in the samples to 2.9.3, otherwise the published zip files of the samples will have the old version.
• Create a new milestone for the next version
• Close the 2.9.3 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 v2.9.3, 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/typesafe/akka/akka-actor_2.13/2.9.3/akka-actor_2.13-2.9.3.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-current-version.sh 2.9.3
  • otherwise check changes and commit the new version to the local git repository

    cd ~/www
    git status
    git add docs/akka/current docs/akka/2.9.3
    git add api/akka/current api/akka/2.9.3
    git add japi/akka/current japi/akka/2.9.3
    git commit -m "Akka 2.9.3"
    

  • push changes to the remote git repository

    cd ~/www
    git push origin master
    

• If this updated 'current' docs - trigger a re-index of the docs for search through Run workflow for the scraper
• Update version in _config.yml in https://github.com/akka/akka.io

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 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 MiMa.latestPatchOf and PR that change (project/MiMa.scala)
• Update akka-dependencies bom and version for Akka module versions in akka-dependencies repo
• Update Akka Guide samples
• Update sbt new templates:
  • Akka Scala
  • Akka HTTP Java
  • Akka HTTP Scala
  • Akka gRPC Java
  • Akka gRPC Scala
• Close this issue

[johanandren]

Docs republished with updated theme