3.3.2 Release procedure

[Kordyjan]

Publish 3.3.2 artifacts to Maven Central via CI:

• On release-3.3.2 branch:
  • In Build.scala: Set baseVersion to 3.3.2
  • In Build.scala: Set referenceVersion to 3.3.1
  • In changelogs add file with a changelog
• Tag the branch as 3.3.2
• Build

Confirm that the tooling is working correctly:

• Metals (@tgodzik)
• Scala CLI
• Scala Native
• Scastie
• Scala DAP (@adpi2)

Update the ecosystem:

• Release 3.3.2 to SDKMAN

Prepare the documentation:

• Merge release-3.3.2 into language-reference-stable
• Publish API docs for 3.3.2
• Add 3.3.2 to the version list in API docs
• Update docs.scala-lang

Announce the releases:

• Make GitHub release public
• Publish a post on https://scala-lang.org/blog
• Close the 3.2.2 milestone

[insiddius]

Actively watching this! Is there an updated ETA?

[sjrd]

⚠️ We might have to bankrupt 3.3.2: playframework/playframework#12418

It produces .tasty files that cannot be read by 3.3.0 and 3.3.1.

[mkurz]

⚠️ We might have to bankrupt 3.3.2: [playframework/playframework#12418]

If you do so, I recommend opening a pull request to make Scala Steward ignore the 3.3.2 release so it stops opening pull requests to upgrade projects, just like I did back a couple of months ago with Play 2.9.0-RC1: scala-steward-org/scala-steward@15ad2e2

[sjrd]

We do that by default:
https://github.com/scala-steward-org/scala-steward/blob/9a8f6d3ab4927ea8a07cbd91cc8e1de44090654d/modules/core/src/main/resources/default.scala-steward.conf#L33-L39
We tell Scala Steward to allow the upgrades to 3.3.2 only after all the release steps are over.

[mkurz]

We tell Scala Steward to allow the upgrades to 3.3.2 only after all the release steps are over.

Ah nice! Didn't know that 👍

[Kordyjan]

3.3.3 hotfix Procedure