scala / scala-dev

Scala 2 team issues. Not for user-facing bugs or directly actionable user-facing improvements. For build/test/infra and for longer-term planning and idea tracking. Our bug tracker is at https://github.com/scala/bug/issues
Apache License 2.0
130 stars 15 forks source link

Release Scala 2.12.20-M1 #872

Closed SethTisue closed 2 months ago

SethTisue commented 2 months ago

Stage

Release

Find the release on Maven Central

Afterwards

SethTisue commented 2 months ago

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 https://github.com/scala/scala-dev/issues/783#issuecomment-918759252 — just need to do SONA_USER and SONA_PASS, a la scala/scala@5ce767fa2b295d0cb4ef56014ede18efbc90ea9c

SethTisue commented 2 months ago

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 commented 2 months ago

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

SethTisue commented 2 months ago

re-STARR PR: https://github.com/scala/scala/pull/10845

lrytz commented 2 months ago

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