Conversation
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueComment |
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.
DO NOT MERGE THIS BEFORE 2026-11-12
Adds a 7-day
min-publish-agecooldown for cargo dependency resolution, socargo add/cargo updateskip crate versions published less than a week ago (the window in which supply-chain compromises are typically detected and yanked).Note: this feature is not available yet. It requires cargo 1.100, which ships with stable Rust 1.100.0 on 2026-11-12 (stabilized in rust-lang/cargo#17335, RFC rust-lang/rfcs#3923). Until then the key is inert: today's stable cargo ignores it silently and current nightly prints a one-line warning. Merging early is safe because versions already in
Cargo.lockare exempt, so builds and CI are unaffected; enforcement starts automatically once toolchains reach 1.100 (CI installs the latest stable at run time, local machines needrustup updateafter the release date).For an urgent bump inside the cooldown window:
CARGO_RESOLVER_INCOMPATIBLE_PUBLISH_AGE=allow cargo update -p <crate>.