Repository navigation
build(renovate): maintain Cargo.lock transitive dependencies weekly - #64
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Renovate already updates direct Rust crates from
Cargo.toml, but full lockfile-only maintenance is disabled by default. As a result, transitive dependencies inCargo.lockcan lag even when direct crates are updated.The current lockfile still pins older releases of
openssl,rustls-webpki,timeandh2, the same kind of gap identified in upstream Treetscom#52. Copying that lockfile would be unsafe because Forkline uses a different crate set.Change
lockFileMaintenancefor Cargo.lock on Mondays.automerge: false). Renovate generates the updates using Cargo and currentCargo.tomlconstraints; CI compiles and tests the resulting lockfile.Expected behavior
Renovate will generate a separate lockfile maintenance PR after the config lands and its next matching run. This PR does not itself upgrade pinned dependencies or resolve outstanding advisories. Review the generated Cargo.lock diff and vulnerability report; dependencies blocked by Cargo.toml constraints need explicit dependency bumps.
Docs: https://docs.renovatebot.com/modules/manager/cargo/ and https://docs.renovatebot.com/configuration-options/#lockfilemaintenance