build(deps): Fix renovate lockfile maintenance #5955
Merged
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.
Description
I recently installed starship (at commit
f353ab4ad1a4dcc9ca9268b3db0dc271842aab10
) viacargo install starship --locked
and received the following warning:I did not like to see that
starship
was being built with a yanked dependency.I cloned
starship/starship
and rancargo update --dry-run
and found that there were many updates available incargo.lock
. I inspected starship's renovate config and saw thatlockFileMaintenance
is supposed to be enabled, which should have prevented the lockfile getting too stale, but it appears to be misconfigured.Renovate's docs suggest configuring lockFileMaintenance differently. I modified the renovate config to enable lockFileMaintenance on a weekly schedule and have it automerge. The renovate docs say automerging lockFileMaintenance is safe.
I also looked through renovate bot's PRs on this repo and verified that no lockfile maintenance PRs had been opened.
Motivation and Context
lockFileMaintenance
is misconfigured, it should be fixed.Screenshots (if appropriate):
How Has This Been Tested?
I am unsure how to test this.
Checklist: