owlstronaut/fix min release age zero#9368
Merged
Merged
Conversation
When the user has `min-release-age=N` in their `.npmrc`, the config flatten function derives a `before` date used by pacote. Whenever pacote spawns a child npm process (e.g. preparing a `git:` or `github:` dep), it forwards `--before=<date>` to the child. The child then loads the same `.npmrc` and the previously declared mutual-exclusivity between `before` and `min-release-age` caused a hard configuration error. This makes the two options coexist: the `exclusive` constraints are removed and both flatten functions resolve to the earlier of the two effective dates, never widening the user's most conservative bound. The `min-release-age` flatten no longer mutates the per-source config object (the prior `obj.before = ...` / `delete obj['min-release-age']` mutations were vestigial and only masked the conflict at the parent level, not in spawned children). `min-release-age` is also added to the `params` arrays for `outdated` and `update` so it remains visible in their command help; it was previously displayed implicitly via the `before` exclusive grouping. Fixes: #9291
owlstronaut
force-pushed
the
owlstronaut/fix-min-release-age-zero
branch
from
825b126 to
da51908
Compare
nishantms
reviewed
May 18, 2026
owlstronaut
force-pushed
the
owlstronaut/fix-min-release-age-zero
branch
from
da51908 to
b0ac494
Compare
nishantms
approved these changes
May 20, 2026
Contributor
|
🎉 Backport to |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
overtakes #9292
This pull request updates the handling of the
beforeandmin-release-ageconfiguration options in npm's configuration system. Previously, these two options were mutually exclusive, but now they can coexist, with clear precedence rules: within the same configuration source,before(an explicit date) takes precedence overmin-release-age(a relative window), and across sources, the standard npm config precedence applies (CLI > env > project > user > global). The documentation, code, and tests have all been updated to reflect and verify this new behavior.