Skip to content

EOL for Sonatype OSSRH requires migration to Sonatype Central #23108

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
WojciechMazur opened this issue May 6, 2025 · 1 comment
Open

EOL for Sonatype OSSRH requires migration to Sonatype Central #23108

WojciechMazur opened this issue May 6, 2025 · 1 comment
Assignees
Labels
area:ci Issues tied with CI/CD workflows area:releases Issues tied to publishing and releasing the language. itype:bug prio:blocker

Comments

@WojciechMazur
Copy link
Contributor

The legacy oss.sonatype.org used in this repository would be soon sunset by June 30 2025. We need to prepare for this by migrating to Sontype Central https://central.sonatype.org/news/20250326_ossrh_sunset/

https://central.sonatype.org/faq/what-is-different-between-central-portal-and-legacy-ossrh/

xerial/sbt-sonatype used by Scala 3 is not yet supporting the new domain xerial/sbt-sonatype#583

@WojciechMazur WojciechMazur added itype:bug prio:blocker stat:needs triage Every issue needs to have an "area" and "itype" label area:ci Issues tied with CI/CD workflows area:releases Issues tied to publishing and releasing the language. labels May 6, 2025
@Gedochao Gedochao removed the stat:needs triage Every issue needs to have an "area" and "itype" label label May 6, 2025
@MateuszKubuszok
Copy link

I think sbt-sonatype support this new workflow, however:

  • currently without snapshots (which might be troublesome if someone wants to always have master available somewhere for testing)
  • with very frequent timeouts (artifacts can be successfully uploaded but we cannot tell as the build is failing)

which is rather discouraging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:ci Issues tied with CI/CD workflows area:releases Issues tied to publishing and releasing the language. itype:bug prio:blocker
Projects
None yet
Development

No branches or pull requests

4 participants