Skip to content

chore: configure dependency minimum release age / cooldown #2426

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Piccirello merged 1 commit into from
May 28, 2026
Merged

chore: configure dependency minimum release age / cooldown #2426

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .npmrc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +1,3 @@
node-linker=hoisted
shamefully-hoist=true
min-release-age=7
Copy link
Copy Markdown
Contributor

@greptile-apps greptile-apps Bot May 28, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Known npm bug with tilde version ranges

min-release-age was introduced in npm CLI 11.10.0 (Feb 2026) and is the correct key here. However, there is a known bug where having this setting in .npmrc causes npm install to fail with --min-release-age cannot be provided when using --before whenever any dependency in the tree uses a ~ version range — npm internally derives --before from the release-age value and then treats it as a conflict. Since most package.json files use tilde ranges, any direct npm install invocation in CI or local dev would be broken by this setting until the bug is resolved upstream.

Prompt To Fix With AI 
This is a comment left during a code review.
Path: .npmrc
Line: 3

Comment:
**Known npm bug with tilde version ranges**

`min-release-age` was introduced in npm CLI 11.10.0 (Feb 2026) and is the correct key here. However, there is a [known bug](https://github.com/npm/cli/issues/9005) where having this setting in `.npmrc` causes `npm install` to fail with `--min-release-age cannot be provided when using --before` whenever any dependency in the tree uses a `~` version range — npm internally derives `--before` from the release-age value and then treats it as a conflict. Since most `package.json` files use tilde ranges, any direct `npm install` invocation in CI or local dev would be broken by this setting until the bug is resolved upstream.

How can I resolve this? If you propose a fix, please make it concise.

Loading