Skip to content

Conversation

@lrytz
Copy link
Member

@lrytz lrytz commented Sep 29, 2025

No description provided.

@lrytz
Copy link
Member Author

lrytz commented Sep 29, 2025

I had to change the release workflow a bit. With the old oss.sonatype.org, there was the possibility to stage a release and test it by adding the staging resolver.

That is no longer possible after the central repository migration, as far as I can tell.

When building a release, we have a downstream job (https://github.com/scala/scala-dist) that builds the tarballs and such, and uploads them to the GitHub release. This can now only be done after the main maven release is on maven central.

Overall that's fine, one real downside is that the https://github.com/scala/scala-dist-smoketest job (which has a small sbt project to test the new release, and also tests the tarballs) now only runs after everything is published...

@lrytz lrytz merged commit d438403 into scala:2.13.x Sep 29, 2025
3 checks passed
@SethTisue SethTisue modified the milestones: 2.13.18, 2.13.17 Sep 30, 2025
@SethTisue SethTisue added the internal not resulting in user-visible changes (build changes, tests, internal cleanups) label Sep 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal not resulting in user-visible changes (build changes, tests, internal cleanups)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants