Central Repository Changelog
2021-05-10 - New Maven Central security capabilities⚓︎
- Great new capabilities are rolling out to help make the components you publish even safer and higher quality!
For more info please check the New Maven Central security capabilities article.
2021-04-05 - New version for The Central Repository Documentation⚓︎
- With this new relaunch of https://central.sonatype.org you will have some new features like Search inside the docs, dark theme and a faster experience.
2021-04-01 - com.github.* is not supported anymore as a valid coordinate⚓︎
com.githubwill no longer be supported as a valid groupId prefix. Github has announced that they will stop redirecting GitHub Pages sites from
*.github.iodomain, and requested that coordinates for individual projects only use
io.githubprefixes from now on.
Current projects already using the
com.githubgroupId in Central are not affected by this change.
2021-02-25 - New server s01.oss.sonatype.org⚓︎
New projects will be allocated in the new server
s01.oss.sonatype.org. Old projects using
oss.sonatype.orginstance are not affected by this change.
For more info please check the New Users on s01.oss.sonatype.org article.
2020-01-15 - Legacy and unsecure HTTP accesses disabled⚓︎
uk.maven.orgwas disabled. Please use the recommended secure https access
For more info please check the Central HTTP deprecation update article.
2019-09-20 - New status page available⚓︎
There is a new status page available at https://status.maven.org. The site provides more granular insights into the status of Maven Central, including uptime for Search, OSSRH, and our Content Delivery Network. Central users will notice that the Maven Central status field at https://status.sonatype.com now redirects to https://status.maven.org for consistency.
The new status page provides system metrics relevant for publishers to the Central repository including publish latency and search indexing latency. Users can now subscribe to receive updates directly via email.
Visit and subscribe to the new status page here. You may also reach the new status page via the integrated status widget in the top right of our homepage.
2019-11-01 - Unsecure access available⚓︎
- Unsecure access
https://insecure.repo1.maven.orgenabled. This URL will continue to be supported after the January 2020 TLS only cutover date. it's recommended to use secure access (
http://repo1.maven.org) where possible.
2014-11-27 - NXRM 2.11 deployed and rule for enforcing valid dependency versions enabled⚓︎
As part of the update to NXRM 2.11 the enforcing of valid dependencies was enabled. This will only affect you if you are using Gradle and the Apache Ivy version range syntax for selecting latest sub-revision e.g.
For more info please check the Enforcing valid dependency versions article.
2014-08-03 - HTTPS Support Launching Now!⚓︎
It is live! Within an extremely short turnaround time the Sonatype Operations team has coordinated certificates and other setup with our excellent CDN provider Fastly and you can now all enjoy the content of the Central Repository via HTTPS/SSL.
Going forward we urge all upstream projects to adopt the secure URL as part of their default configuration. In the mean time we have updated the instructions for consuming components from the Central Repository with all the details necessary for your repository manager, build tool or other access mode you are using.
We hope you enjoy this new feature and look forward to your feedback!
2014-06-11 - Change of IP⚓︎
In an ongoing effort to improve availability for https://oss.sonatype.org, we are moving that host behind some new load balancing infrastructure. The new load balancers have wider support for SSL protocols and ciphers than the current host. So, as a side benefit, intermittent deployment errors caused by SSL handshake issues, should go away.
The IP address to which oss.sonatype.org resolves will change during the regular Sonatype scheduled maintenance window, Wednesday night, 11 June 2014, at or around 9PM EDT. The new IP address will be:
For the majority of OSSRH users (who access it by hostname), this change should be invisible. Organizations who have outbound firewall rules set up to allow traffic to a specific IP address will need to update their rules to use the new IP address.