Contribution

• I'd be willing to implement this feature (contributing guide)

Describe the user story

Currently, pnpm outdated does not consider minimumReleaseAge when showing the latest versions. This makes it difficult to reconcile the updates that will be done by pnpm update (which seems to account for minimumReleaseAge), and makes it difficult to review the exact version that a package should/will be updated to.

Describe the solution you'd like

Account for minimumReleaseAge and minimumReleaseAgeExclude when showing the latest version in pnpm outdated.

Describe the drawbacks of your solution

Users might not know there is a newer version out, but the point of minimumReleaseAge is to delay updates so having a newer version out that does not meet the minimumReleaseAge is irrelevant to the user using minimumReleaseAge.

Describe alternatives you've considered

Manually checking npm for the latest version that meets the minimumReleaseAge.

• This does not scale when there are a lot of packages that might be outdated