-
Notifications
You must be signed in to change notification settings - Fork 3k
Open
Labels
manager:npmpackage.json files (npm/yarn/pnpm)package.json files (npm/yarn/pnpm)minimumReleaseAgepriority-3-mediumDefault priority, "should be done" but isn't prioritised ahead of othersDefault priority, "should be done" but isn't prioritised ahead of others
Description
Describe the proposed change(s).
When minimumReleaseAge is specified, we should make sure that all npm calls include the flag, so we don't accidentally install dependencies that may be newer.
We can't specify this when using min-release-age configuration (via)
before:
If the requested version is a
dist-tagand the given tag does not pass the--beforefilter, the most recent version less than or equal to that tag will be used. For example,foo@latestmight installfoo@1.2even thoughlatestis2.0.This config cannot be used with:
min-release-age
And for min-release-age:
This flag is a complement to
before, which accepts an exact date instead of a relative number of days.This config cannot be used with:
before
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
manager:npmpackage.json files (npm/yarn/pnpm)package.json files (npm/yarn/pnpm)minimumReleaseAgepriority-3-mediumDefault priority, "should be done" but isn't prioritised ahead of othersDefault priority, "should be done" but isn't prioritised ahead of others