CI: use native Cargo dependency cooldown feature - #2552
Merged
Merged
Conversation
marxin
force-pushed
the
dependency-cooldown
branch
from
September 19, 2026 08:24
3d11cab to
3acfdeb
Compare
davidlattimore
left a comment
Member
There was a problem hiding this comment.
Nice! I'd been thinking it'd be good if we could take advantage of that feature somehow
davidlattimore
approved these changes
Sep 20, 2026
Member
|
I was just wondering about what dependabot will do and found that it has a 3 day cooldown by default - introduced relatively recently. So I guess this CI job will mostly force us to slow down if people do a manual cargo update. edit: I see this is mentioned in the article you linked, so probably isn't news to you :) |
Collaborator
Author
|
Yes, I know it aligns nicely with Dependabot ;) |
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
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.
With the increasing number of supply chain attacks (1), Cargo introduced a native cooldown mechanism that will be stabilized in
1.100(if I'm not mistaken): rust-lang/cargo#17335. So far available on+nightlyCargo version.The check can properly detect if a version from
Cargo.tomldoes not fulfill the cooldown period, but there's one drawback connected toCargo.lockfile dependencies - these are ignored and only a warning is reported. So until the feature is stabilized, one must use nightly compiler for updating.Sample output if accidentally updated to latest:
If sticking to a fresh release in
Cargo.toml:And the linked blog post is also pretty nice reading: https://cooldowns.dev/
Footnotes
https://blog.rust-lang.org/2026/08/20/supply-chain-attack-on-arrayref/ ↩