-
-
Notifications
You must be signed in to change notification settings - Fork 18
chore: add 24-hour package manager cooldown #1694
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.
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -7,4 +7,6 @@ packageExtensions: | |
| dependencies: | ||
| node-gyp: "^10.0.1" | ||
|
|
||
| npmMinimalAgeGate: 1440 | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🧩 Analysis chain🌐 Web query:
💡 Result: No, npmMinimalAgeGate is not supported in Yarn 3.4.1. It was first supported in Yarn 4.10.0, as per the official GitHub pull request Citations:
This config key is not supported until Yarn 4.10.0. Line 10 introduces an unrecognized setting that causes Unblock immediately by removing this line, or upgrade Minimal fix (remove unsupported key)-npmMinimalAgeGate: 1440🤖 Prompt for AI Agents |
||
|
|
||
| yarnPath: .yarn/releases/yarn-3.4.1.cjs | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
npmMinimalAgeGatedoes not appear to be a recognized Yarn configuration option for the pinned Yarn version (yarnPath: .yarn/releases/yarn-3.4.1.cjs). I couldn’t find the setting name in that Yarn release bundle, and Yarn 3.x typically fails with “Unrecognized configuration setting” for unknown keys, which would break installs/CI. Consider either upgrading Yarn to a version that supports this setting (and updatingyarnPathaccordingly) or using an alternative approach (e.g., registry proxy/mirroring) that’s compatible with Yarn 3.4.1.