Skip to content

chore(cargo): enforce 14-day min-publish-age for crates.io deps #183

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
storopoli merged 2 commits into from
Sep 2, 2026
Merged

chore(cargo): enforce 14-day min-publish-age for crates.io deps #183

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
aebfb49
chore(cargo): enforce 14-day min-publish-age for crates.io deps
storopoli Sep 2, 2026
73edae1
chore(cargo): set incompatible-publish-age to deny explicitly
storopoli Sep 2, 2026
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
19 changes: 19 additions & 0 deletions .cargo/config.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
# Cooldown for crates.io dependencies (RFC 3923, `min-publish-age`).
# Versions published less than 14 days ago are not selected by the resolver
# unless they are already in `Cargo.lock`. Matches the Dependabot cooldown.
# Urgent override for a single resolve:
# CARGO_RESOLVER_INCOMPATIBLE_PUBLISH_AGE=allow cargo update -p <crate>

# Stable cargo ignores this table. Nightly cargo needs it until the feature
# is stable (Rust 1.100, 2026-11-12); remove it once the toolchain has it.
[unstable]
min-publish-age = true

[registry]
global-min-publish-age = "14 days"
Comment on lines +9 to +13

@chatgpt-codex-connector chatgpt-codex-connector Bot Sep 2, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Update the pinned Cargo before enabling this policy

The workspace still pins nightly-2026-07-01 in rust-toolchain.toml, whose Cargo predates the min-publish-age implementation. Cargo silently accepts unknown entries under [registry], so this setting is inert with the repository toolchain and cargo update can still resolve a freshly published crate; the missing expected age suffix in the recorded dry run is consistent with that. Bump the pinned nightly to a release containing the feature (or defer this config) before relying on it as a supply-chain control.

Useful? React with 👍 / 👎.


# Reject too-new versions even when a user-level cargo config sets "allow".
# The CARGO_RESOLVER_INCOMPATIBLE_PUBLISH_AGE environment variable still
# overrides this for one-off updates.
[resolver]
incompatible-publish-age = "deny"
Loading