Skip to content
Merged
Changes from all commits
Commits
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
6 changes: 6 additions & 0 deletions renovate.json
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,7 @@
"dependencyDashboardApproval": true,
"minimumReleaseAge": "3 days",
"postUpdateOptions": ["yarnDedupeHighest"],
"rangeStrategy": "bump",
Comment thread
cursor[bot] marked this conversation as resolved.
"skipInstalls": false,
"statusCheckNames": {
"artifactError": null,
Expand All @@ -13,6 +14,11 @@
"minimumReleaseAge": null
},
"packageRules": [
{
"description": "Restores the default for peer ranges, which `rangeStrategy` above would otherwise override. Peer ranges are deliberately wide, so they get broadened rather than raised.",

@mcmire mcmire Sep 21, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Didn't realize that this was the default for peer dependencies (source here). I would think that Renovate would leave peer deps alone, but I guess that strategy may limit the degree could upgrade production deps. I guess we can see how well this strategy works out in practice. We don't have many peer deps anyway so maybe it doesn't matter.

"matchDepTypes": ["peerDependencies"],
"rangeStrategy": "widen"
},
{
"description": "Mirrors npmPreapprovedPackages in .yarnrc.yml, which exempts these from the install-time age gate.",
"matchPackageNames": [
Expand Down
Loading