Repository navigation
fix(deps): align Dependabot updates with pnpm release-age guard - #1059
AchoArnold wants to merge 1 commit into
Conversation
Declare a three-day npm cooldown and share the existing 24-hour release-age gate with Dependabot's pnpm resolver. Keep monthly schedules and security updates unchanged. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: f27d8f52-9620-4ee2-a564-ec4870a5f840
Up to standards ✅🟢 Issues
|
[Medium impact] The PR appears safe to merge. SummaryAdds a three-day Dependabot cooldown for
Reviews (1) · Last reviewed commit: "fix(deps): align Dependabot updates with..." · Reviewed by Greptile |
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues are identified for the web dependency-update policy changes.
No open issues 🎉
What changed in this PR
Aligns routine Dependabot updates for the web frontend with pnpm’s 24-hour release-age guard, reducing update PRs that fail local installation checks.
Changes:
- Declares a three-day cooldown for
/webnpm version updates. - Explicitly sets pnpm’s release-age guard to 1,440 minutes so compatible Dependabot resolvers also apply it to transitive dependencies.
- Leaves monthly schedules, other ecosystem policies, build permissions, dependencies, and lockfiles unchanged.
| File | Description |
|---|---|
web/pnpm-workspace.yaml |
Adds the explicit 24-hour pnpm release-age setting. |
.github/dependabot.yml |
Adds a three-day cooldown for web npm version updates. |
Review effort: Balanced
Goal
Avoid routine npm version-update PRs that immediately fail pnpm's 24-hour release-age guard, including fresh transitive packages pulled in while regenerating the lockfile.
Changes
/webnpm version updates.minimumReleaseAge: 1440inweb/pnpm-workspace.yamlso pnpm 10.16+ used by Dependabot inherits the same 24-hour guard as local pnpm 11, rather than relying on pnpm 11's implicit default.Why both settings
GitHub currently documents a three-day default cooldown even without configuration: declaring it alone is not the fix. The explicit workspace setting is the substantive change: pnpm applies it during dependency resolution, including transitive packages. Current Dependabot code reads the native setting and applies the longer cooldown/native window during regular pnpm updates.
Limits
Verification
git diff main...HEAD --checkpassed.pnpm config get minimumReleaseAgereturned1440on installed pnpm 11.3.0.References