build(deps): add Dependabot cooldown to clear the pnpm age gate#2009
Merged
Conversation
Dependabot writes new versions into pnpm-lock.yaml without honoring .npmrc, so CI failed on `pnpm install --frozen-lockfile` with ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION whenever a release was less than 24h old. Add a 2-day cooldown to the npm ecosystem, mirroring the install policy. Cooldown is day-granular, so it must be strictly greater than minimum-release-age (1440 min = 1 day). The exclude list mirrors pnpm-workspace.yaml#minimumReleaseAgeExclude. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for gethinode-demo ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This was referenced Jul 13, 2026
Merged
Merged
Merged
Merged
Collaborator
Author
|
🎉 This PR is included in version 3.0.3 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
1 participant
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.
Problem
Since the pnpm migration,
.npmrcsetsminimum-release-age=1440(24h). pnpm enforces this against lockfile entries at install time, not only at resolution time. Dependabot writes the new version intopnpm-lock.yamlwithout honoring.npmrc, so every Dependabot PR for a package published less than 24h ago fails CI onpnpm install --frozen-lockfile:This fails on every OS/Node combination and blocks auto-merge. Live examples: gethinode/mod-utils#341, gethinode/mod-blocks#153.
Fix
Mirror the install policy in the Dependabot policy via
cooldown, rather than weakening either side.The invariant: Dependabot's cooldown must be strictly greater than pnpm's
minimum-release-age. Cooldown is day-granular and 1440 minutes is exactly 1 day, sodefault-days: 2is the smallest safe value.cooldown.excludemirrorspnpm-workspace.yaml#minimumReleaseAgeExcludeso the two policies stay in step.Verified the config parses and validates against the official Dependabot JSON schema (
default-daysandexcludeare both legal keys).Scope
24 repos carry
minimum-release-age=1440+ an npm Dependabot ecosystem and none has a cooldown. This PR doeshinode;mod-template(the seed for new modules) gets the same change so the bug isn't inherited. The remaining 22 follow once this is proven green.Note
Dependabot security updates ignore
cooldownby design, so a security PR for a very fresh release can still trip the gate. Those are rare and self-heal on re-run after 24h.🤖 Generated with Claude Code