Describe the proposed change(s).
Sonatype are the hosts of Maven Central. Maven Central receives a very large number of requests, so Sonatype has taken steps to try to rate limit the largest users. It's been a progressive process and the latest news I'm aware of is here: https://www.sonatype.com/blog/beyond-ips-addressing-organizational-overconsumption-in-maven-central
Some Renovate users may be amongst the heavy users of Maven Central, potentially from their developer machines or CI/CD alone, but also possibly due to Renovate use too.
We have made improvements to Maven caching in Renovate although it does rely on the datasource cache being persistent. By default the cache is file-based so anyone using ephemeral Renovate jobs won't benefit from such a cache across runs.
We should make sure that we are issuing a logger warning any time Renovate receives a 429 from Maven Central, and ideally also note whether a Redis datasource cache is in use or not. The warning message should be different based on whether a persistent cache is noted or not. We should add documentation to the Maven datasource in Renovate docs about Maven Central rate limiting and Renovate caching, and direct users to there if they get rate limited.
Such messages should be shown clearly in the Dependency Dashboard
Describe the proposed change(s).
Sonatype are the hosts of Maven Central. Maven Central receives a very large number of requests, so Sonatype has taken steps to try to rate limit the largest users. It's been a progressive process and the latest news I'm aware of is here: https://www.sonatype.com/blog/beyond-ips-addressing-organizational-overconsumption-in-maven-central
Some Renovate users may be amongst the heavy users of Maven Central, potentially from their developer machines or CI/CD alone, but also possibly due to Renovate use too.
We have made improvements to Maven caching in Renovate although it does rely on the datasource cache being persistent. By default the cache is file-based so anyone using ephemeral Renovate jobs won't benefit from such a cache across runs.
We should make sure that we are issuing a logger warning any time Renovate receives a 429 from Maven Central, and ideally also note whether a Redis datasource cache is in use or not. The warning message should be different based on whether a persistent cache is noted or not. We should add documentation to the Maven datasource in Renovate docs about Maven Central rate limiting and Renovate caching, and direct users to there if they get rate limited.
Such messages should be shown clearly in the Dependency Dashboard