Renovate respects pnpm minimumReleaseAge, but ignores minimumReleaseAgeExclude

[zboro]

How are you running Renovate?

Self-hosted Renovate

Which platform you running Renovate on?

GitHub Enterprise Server

Which version of Renovate are you using?

41.173.1

Please tell us more about your question or problem

We have setup where we have minimumReleaseAge configured both in renovate and pnpm (same values), but we exclude some packages from it. In renovate by setting minimumReleaseAge to 0 for that package in package rules and for pnpm by adding it to minimumReleaseAgeExclude. Those packages can be installed without issue as soon as they are available and renovate will also open PRs for them. However, in those PRs it will fail with ERR_PNPM_NO_MATCHING_VERSION. If enough time passed between package version release and opening PR, renovate will update it without issues. That's why it looks to me like renovate somehow respects pnpm minimumReleaseAge, but applies it also to packages in minimumReleaseAgeExclude.

Logs (if relevant)

No response

[jamietanna]

Yep, per #39168 / #38393 Renovate doesn't currently support the ability to modify/infect configuration from minimumReleaseAgeExclude

Would you be thinking that Renovate would read what's in pnpm's minimumReleaseAgeExclude, and therefore imply that even if Renovate's minimumReleaseAge is set on the package, it should instead follow what pnpm's config says?

[zboro]

Based on those other discussions I would assume renovate would ignore pnpm's configs completely and try to update package. I wouldn't be surprised if renovate threw error or failed to update lock file in cases where pnpm blocks it from fetching new version. That would be fine and we would just need to keep renovate and pnpm configs in sync. It would only break for security updates like that other discussion mentions.
Problem is that even though package is in minimumReleaseAgeExclude and therefore pnpm won't block anything, renovate somehow still treats that version as blocked.

[jamietanna]

Problem is that even though package is in minimumReleaseAgeExclude and therefore pnpm won't block anything, renovate somehow still treats that version as blocked.

To confirm, you mean:

• Renovate has configuration minimumReleaseAge i.e. for all packages
• a given package has a pending update
• pnpm config for minimumReleaseAgeExclude says not to require minimum release age checks for the package
• Renovate does not raise a PR

?

[jamietanna]

Can you confirm what Renovate's minimumReleaseAge and what pnpm's minimumReleaseAge are set to?

[zboro]

renovate opens PR, but it fails to update pnpm lock file and comments PR with ERR_PNPM_NO_MATCHING_VERSION error
settings are:

• renovate minimumReleaseAge is 7 days by default for all packages
• renovate minimumReleaseAge is overridden to 0 for excluded package
• pnpm minimumReleaseAge is set to 10080
• pnpm minimumReleaseAgeExclude has excluded package

[jamietanna]

If Renovate's minimumReleaseAge and pnpm's minimumReleaseAgeExclude seem to be set up correctly (to 7 days), but Renovate opens a PR and pnpm isn't happy, I think we'll need a minimal repro to get more info

[github-actions[bot]]

Hi there,

Please help this Discussion progress by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the reproduction in your own repository. Ensure it's actually minimal (no unnecesary dependencies or config), or it will be rejected by maintainers.
5. Install the Renovate app to verify that what you say happens (or doesn't happen) reproduces.
6. Fill out the information in your repository's README.md. What you describe there should reflect what you see in this repo, with the hosted app, and not what you saw in your original repo/environment.
7. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.
8. Add a Discussion comment mentioning that the reproduction repo is now available and linked.

If you need help with running Renovate on your minimal reproduction repository, please refer to our Running Renovate guide.
Good luck,

The Renovate team

[RahulGautamSingh]

Should be fixed by: #40020