Skip to content

renovate: Fix cargo in-range updates being silently dropped #199

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jeckersb merged 1 commit into from
Jun 2, 2026
Merged

renovate: Fix cargo in-range updates being silently dropped #199

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
14 changes: 14 additions & 0 deletions renovate-shared-config.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -136,6 +136,20 @@
"groupName": "Rust",
"enabled": true
},
// Restore cargo's default rangeStrategy for in-range updates.
//
// ":preserveSemverRanges" sets rangeStrategy=replace globally, which means
// Renovate only acts when a new version falls *outside* the existing range.
// For cargo deps like `tar = "0.4.43"` (i.e. ^0.4.43), patch releases such
// as 0.4.46 are in-range and would be silently ignored - Cargo.lock never
// gets updated. Restoring `update-lockfile` here makes Renovate bump
// Cargo.lock for in-range updates while still using `replace` for
// out-of-range ones (the same as cargo's native default behaviour).
{
"description": ["Restore update-lockfile rangeStrategy for cargo (overrides :preserveSemverRanges)"],
"matchManagers": ["cargo"],
"rangeStrategy": "update-lockfile"
},
// Group Docker dependencies
{
"description": ["Docker dependencies"],
Expand Down