Maven Central documentation is stale

[jsoref]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/actions/use-cases-and-examples/publishing-packages/publishing-java-packages-with-maven

What part(s) of the article would you like to see updated?

All mentions of OSSRH and oss.sonatype.org should be updated, or a section section/page should be added.

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

If you use https://oss.sonatype.org or https://s01.sonatype.org to publish, you are publishing via the Legacy OSSRH service. If you are publishing via a build tool integration, this might be configured as a default, so check the plugin's documentation to be sure, if you didn't manually specify a URL.

Apparently Maven Central is now a new thing which is something other than OSSRH.

Additional information

As I'm trying to set up publishing to Maven Central. Apparently that was replaced in mid 2024.

As I have no idea how to do it and can't really figure it out, I can't give particularly good information about how to fix this page, but at the very least a warning could be added:

Warning

This page is out of date and refers to the Legacy OSSRH Service.

[nguyenalex836]

@jsoref Thank you for raising this issue! I'll get this triaged for review ✨ Our team will provide feedback regarding the best next steps for this issue - thanks for your patience! 💛

[github-actions]

Thanks for opening an issue! We've triaged this issue for technical review by a subject matter expert 👀

[subatoi]

@jsoref 👋 I'm going to transfer this to an internal issue to fix it there. I'll update this issue when that's complete. Thank you for raising it!

[docs-bot]

Thank you for opening this issue! Updates to this documentation must be made internally. I have copied your issue to an internal issue, so I will close this issue.

[subatoi]

Just to follow up: this article now contains a warning. Many thanks for reporting this!