⬆️ Update dependency tmp@<0.2.4 to ~0.2.5 - autoclosed#6884
⬆️ Update dependency tmp@<0.2.4 to ~0.2.5 - autoclosed#6884renovate[bot] wants to merge 1 commit into
Conversation
|
914fa34 to
d3072db
Compare
@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 #6884 +/- ##
=======================================
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:
|
|
@claude prepare a pr to configure renovate in a way that it would not open such prs. I don't want prs changing the overrides, they can be bump but the package.json should stay untouched |
|
Claude finished @dubzzz's task in 2m 31s —— View job Task: Configure Renovate to skip overrides updates
ResultOpened PR #6891 — 🔧 Disable Renovate updates on pnpm overrides. The new rule appended to {
"matchFileNames": ["package.json"],
"matchDepTypes": ["pnpm.overrides"],
"enabled": false
}This stops Renovate from opening PRs (like this one, #6884) that rewrite the override constraint strings in the root |
## Description Configure Renovate so it stops opening PRs that change the `pnpm.overrides` entries in the root `package.json`. These overrides are intentionally pinned via tilde ranges (see #6888) so that patch-level updates flow naturally through `pnpm-lock.yaml` (already covered by `lockFileMaintenance`), without rewriting the constraint string in `package.json` on every patch release. Renovate currently still opens PRs (e.g. #6884) to bump those override constraints — this change disables that behavior. The new `packageRule` matches the `pnpm.overrides` `depType` on the root `package.json` and 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_ - [x] I have a full understanding of every line in this PR — whether the code was hand-written, AI-generated, copied from external sources or produced by any other tool - [ ] I flagged the impact of my change (minor / patch / major) either by running `pnpm run bump` or by following the instructions from the changeset bot - [x] I kept this PR focused on a single concern and did not bundle unrelated changes - [x] I followed the [gitmoji](https://gitmoji.dev/) specification for the name of the PR, including the package scope (e.g. `🐛(vitest) Something...`) when the change targets a package other than `fast-check` - [ ] I added relevant tests and they would have failed without my PR (when applicable) Co-authored-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com> Co-authored-by: Nicolas DUBIEN <[email protected]>
This PR contains the following updates:
~0.2.4→~0.2.5Release Notes
raszi/node-tmp (tmp@<0.2.4)
v0.2.5Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.