🔧 Disable Renovate updates on pnpm overrides#6891
Conversation
Co-authored-by: Nicolas DUBIEN <[email protected]>
|
@fast-check/ava
fast-check
@fast-check/jest
@fast-check/packaged
@fast-check/poisoning
@fast-check/vitest
@fast-check/worker
commit: |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6891 +/- ##
=======================================
Coverage 94.75% 94.75%
=======================================
Files 211 211
Lines 5778 5778
Branches 1527 1528 +1
=======================================
Hits 5475 5475
Misses 295 295
Partials 8 8
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Description
Configure Renovate so it stops opening PRs that change the
pnpm.overridesentries in the rootpackage.json.These overrides are intentionally pinned via tilde ranges (see #6888) so that patch-level updates flow naturally through
pnpm-lock.yaml(already covered bylockFileMaintenance), without rewriting the constraint string inpackage.jsonon every patch release. Renovate currently still opens PRs (e.g. #6884) to bump those override constraints — this change disables that behavior.The new
packageRulematches thepnpm.overridesdepTypeon the rootpackage.jsonand disables updates for it. Lockfile maintenance keeps picking up resolvable patch versions automatically.Checklist
— Don't delete this checklist and make sure you do the following before opening the PR
pnpm run bumpor by following the instructions from the changeset bot🐛(vitest) Something...) when the change targets a package other thanfast-check