Skip to content

chore: add 24h package manager cooldown #11

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
nrjinua merged 1 commit into from
Apr 21, 2026
Merged

chore: add 24h package manager cooldown #11

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
@@ -0,0 +1 @@
min-release-age=1
Copy link

Copilot AI Mar 31, 2026

Choose a reason for hiding this comment

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

Repo workflows use npm ci/npm publish (not pnpm/yarn), and min-release-age is not a standard npm config key. If npm ignores this setting, the intended 24h “cooldown” won’t actually be enforced. Consider either (a) switching CI/dev to the package manager that supports this option, or (b) using an npm-supported mechanism and documenting it here so the behavior is guaranteed.

Copilot uses AI. Check for mistakes.
Loading