Release Scala 2.12.20-M1

[SethTisue]

Stage

• Make sure there are no stray staging repos on Sonatype
• Trigger a custom build on travis
  • Select the correct branch
  • Custom config: before_script: export SCALA_VER_BASE=2.12.20 SCALA_VER_SUFFIX=-M1
  • https://app.travis-ci.com/github/scala/scala/builds/271910340
• Create the scala/scala tag locally: git tag -s -m "Scala 2.12.20-M1" v2.12.20-M1 1f657ec1ad6e1c8376e59ac39ec8bec1f4a9a80c

Release

• Push scala/scala tag: git push https://github.com/scala/scala.git v2.12.20-M1
• Promote staging repos: st_stagingRepoPromote [scala-repo], st_stagingRepoPromote [modules-repo] (or use oss.sonatype.org web UI)

Find the release on Maven Central

• https://repo1.maven.org/maven2/org/scala-lang/scala-compiler/2.12.20-M1/

Afterwards

• Create a scala/scala PR to:
  • update starr.version in /versions.properties

[SethTisue]

https://app.travis-ci.com/github/scala/scala/jobs/625182602 has:

[error] java.net.ProtocolException: Server redirected too many  times (20)

sigh, need to regenerate secret, using instructions at #783 (comment) — just need to do SONA_USER and SONA_PASS, a la scala/scala@5ce767f

[SethTisue]

refreshing those secrets didn't work, same errors at https://app.travis-ci.com/github/scala/scala/jobs/625183478

I think the mistake I made was to put the actual username/password in the secrets, instead of the Sonatype user token

I will try again

[SethTisue]

it worked this time, artifacts are en route to Maven Central

[SethTisue]

re-STARR PR: scala/scala#10845

[lrytz]

I think the mistake I made was to put the actual username/password in the secrets, instead of the Sonatype user token

right, i think there was a recent change at sonatype to only accept the token, no longer the password.

https://support.sonatype.com/hc/en-us/articles/360049469534-401-Content-access-is-protected-by-token-when-accessing-repositories