Issue with minimumReleaseAge and matchRegistryUrls

[berke581]

How are you running Renovate?

Self-hosted Renovate CLI

Which platform you running Renovate on?

GitLab (.com or self-hosted)

Which version of Renovate are you using?

43.102.2

Please tell us more about your question or problem

I’m trying to set the minimumReleaseAge config in Renovate, but only for 3rd party dependencies. Here’s my approach:

module.exports = {
    internalChecksFilter: "strict",
    minimumReleaseAge: "2 days",
    // ...
    packageRules: [
        {
            matchRegistryUrls: ["/org-name/"],
            minimumReleaseAge: null,
        },
        // ...

However, I’ve hit a puzzling issue. For a 3rd party Maven dependency, minimumReleaseAge: null seems to apply, even though I expect it to only apply to internal dependencies (where the registry URL matches /org-name/). As a result, recent versions are updated immediately (for Maven deps), which isn’t what I want. Here’s an example log (a few days old), and you can see the registryUrl and registryUrls values:

{"currentValue":"2.42.26","currentVersion":"2.42.26","currentVersionAgeInDays":7,"currentVersionTimestamp":"2026-04-01T21:49:49.000Z","datasource":"maven","depName":"software.amazon.awssdk:s3","depType":"compile","fileReplacePosition":1938,"fixedVersion":"2.42.26","homepage":"https://aws.amazon.com/sdkforjava","isSingleVersion":true,"packageName":"software.amazon.awssdk:s3","registryUrl":"https://repo.maven.apache.org/maven2","registryUrls":["https://repo.maven.apache.org/maven2"],"respectLatest":false,"versioning":"maven","warnings":[],"updates":[{"bucket":"non-major","newVersion":"2.42.31","newValue":"2.42.31","releaseTimestamp":"2026-04-08T22:14:07.000Z","newVersionAgeInDays":0,"newMajor":2,"newMinor":42,"newPatch":31,"updateType":"patch","isBreaking":false,"libYears":0.01922431506849315,"branchName":"renovate/main-all-minor-patch"}]}

When I remove the packageRules entry with matchRegistryUrls, it behaves as expected. The new version age changes and updates are delayed according to the config (And also, you can see in the previous log newVersionAgeInDays was set to 0, and in the new log 2, as we expect since we want the minimumReleaseAge to apply here):

{"currentValue":"2.42.26","currentVersion":"2.42.26","currentVersionAgeInDays":7,"currentVersionTimestamp":"2026-04-01T21:49:49.000Z","datasource":"maven","depName":"software.amazon.awssdk:s3","depType":"compile","fileReplacePosition":1938,"fixedVersion":"2.42.26","homepage":"https://aws.amazon.com/sdkforjava","isSingleVersion":true,"packageName":"software.amazon.awssdk:s3","registryUrl":"https://repo.maven.apache.org/maven2","registryUrls":["https://repo.maven.apache.org/maven2"],"respectLatest":false,"versioning":"maven","warnings":[],"updates":[{"bucket":"non-major","newVersion":"2.42.29","newValue":"2.42.29","releaseTimestamp":"2026-04-06T22:05:18.000Z","newVersionAgeInDays":2,"newMajor":2,"newMinor":42,"newPatch":29,"updateType":"patch","isBreaking":false,"pendingVersions":["2.42.30","2.42.31"],"libYears":0.013728088533739219,"branchName":"renovate/main-all-minor-patch"}]}

I also have this rule in my global Renovate config under packageRules, which could be affecting things: But I don't really understand it since the logs clearly state the 3rd party maven repo for registryUrls:

        {
            matchDatasources: ["maven"],
            registryUrls: ["https://org-name.jfrog.io/artifactory/repo/", "https://repo.maven.apache.org/maven2"]
        }

Any insights or advice would be appreciated!

Logs (if relevant)

Logs

I think necessary logs are provided in the description, I can share more as requested.