Cargo Dependency Cooldowns: min-publish-age in Rust 1.100
Rust 1.100 lets Cargo skip crate versions newer than an age you set. How a dependency cooldown works, how to let a security fix through, and what it cannot catch.

What is a dependency cooldown in Cargo?
A dependency cooldown tells Cargo to ignore crate versions published more recently than an age you choose, such as 7 days, unless the version is already in Cargo.lock. In Rust 1.100 it is set with registry.global-min-publish-age. It buys time for scanners and maintainers to catch a bad release. It is not an audit.
On August 20, 2026, the Rust Security Response Team deleted a malicious release of arrayref. The popular crate had been republished to depend on proc-macro1, a crate whose build script downloaded a payload. The team's timeline is precise: arrayref 0.3.10 was published at 07:15 UTC and deleted at 08:41 UTC. Online for 86 minutes. Two more crates by the same author were hit the same morning.
Eighty-six minutes is a short window. It was still long enough for any cargo update that ran inside it to pull the bad version. A dependency cooldown closes that window on purpose. You tell Cargo to ignore versions younger than an age you choose, and the newest release waits until scanners, maintainers and the people who like living on the edge have had a look.
Rust 1.100.0 is dated November 12, 2026 in the project's release notes, and its Cargo section introduces "minimum publish age configurations, also known as dependency cooldowns." The design is RFC 3923. This note covers what the setting does, how to run it without blocking a security fix, and why Remade treats it as one gate among several in the Trust band, not as the gate.
What a dependency cooldown changes in Cargo
A registry records when each version was published. Cargo calls that the pubtime. With a cooldown set, a version whose pubtime is newer than the configured min-publish-age is treated as pubtime-incompatible, and the resolver skips it, unless that version is already recorded in Cargo.lock. If no compatible version is old enough, resolution fails with an error instead of quietly picking the new one.
The default is off. In the Cargo configuration reference, registry.global-min-publish-age defaults to "0", which allows every version, and both it and resolver.incompatible-publish-age are marked "Respected as of 1.100+." A registry that does not report a publish time is not checked. So the dependency cooldown is something a team chooses, writes down and reviews, like any other supply-chain rule.
The RFC is candid about why it exists. It points to recent attacks on the npm ecosystem and says some supply-chain attacks are found by automated scanners shortly after a version is published, so waiting gives those scanners time to work. The same RFC adds a second benefit. New versions can carry plain bugs, and a cooldown lets the ecosystem's early adopters find them first.
How to set a dependency cooldown for a Rust project
Three pieces make a dependency cooldown usable in practice: the setting, an escape hatch for urgent fixes, and a job that still watches the newest versions.
Set the cooldown in .cargo/config.toml
The setting lives in Cargo configuration, not in Cargo.toml. A project-level .cargo/config.toml keeps it in review with the code:
[registry]
global-min-publish-age = "7 days"
Values are an integer followed by seconds, minutes, hours, days, weeks or months, and the docs say "0", "N days" and "N weeks" are the usual choices. A private registry can carry its own value under [registries.<name>] with min-publish-age. Pick a number you can defend in a review. The Cargo docs use 7 days in their example, and the RFC uses 14. Longer means more time for a report to land, and more time behind the newest fixes.
Let urgent security fixes through on purpose
A cooldown that blocks the patch for a critical advisory is worse than no cooldown. The resolver documentation describes the override: setting resolver.incompatible-publish-age to allow, combined with cargo update --precise, pulls in one specific version and its transitive dependencies.
CARGO_RESOLVER_INCOMPATIBLE_PUBLISH_AGE=allow cargo update -p some-crate --precise 1.2.4
Make that a named step with a reason in the commit message, so the exception is visible later. An override that happens silently is just the old habit with extra syntax.
Keep a canary job on the newest versions
The RFC suggests a split that fits a cooldown well. Local work and release builds keep the cooldown. One CI job sets the override, runs cargo update, and builds and tests against the newest versions. Breakage shows up in that job before it reaches anyone's release, and the cooldown still governs what ships.
What a dependency cooldown does not cover
A dependency cooldown is a delay, and a delay only helps if someone uses the time. Know its edges before you lean on it.
A dependency cooldown is not an audit
Time does not read code. A malicious crate that nobody reports in seven days is just as malicious on day eight. RFC 3923 says it directly: the feature "should not be relied upon for security by itself." Audits are a separate layer. The cargo vet criteria note covers how safe-to-run and safe-to-deploy record that someone actually looked, and cargo update is not a security model is the house argument for owning the graph instead of trusting the newest number.
Lockfiles and versions you already have
The cooldown governs new picks. A version already in Cargo.lock stays, whatever its age. If a bad release reached your lockfile before you set a cooldown, the setting will not remove it. After the arrayref incident, the Rust blog published a command to search the local registry cache for the affected files. That kind of check, plus advisory scanning on the lockfile, is still your job.
Where Remade stands on dependency cooldowns
Remade's crates live in the Remade-With-Rust organization, and the Trust band is where supply-chain tooling sits. Deputy is the house answer for keeping a dependency graph offline, reviewing changes and deploying on purpose, and its repo landing has the conversion pin. This note does not claim that any Remade crate's CI sets a dependency cooldown today. The recommendation is the one above: a reviewed cooldown in .cargo/config.toml, a named override for security fixes, a canary job, and audits on top. A delay buys time. The ledger decides what ships.
FAQ
Quick answers for builders evaluating this technology.
Which Rust version supports min-publish-age?
The Cargo documentation marks registry.global-min-publish-age and resolver.incompatible-publish-age as respected from Rust 1.100. Rust 1.100.0 is dated November 12, 2026 in the project's release notes. Older toolchains do not apply the setting.
Does a dependency cooldown change versions already in Cargo.lock?
No. A version already recorded in Cargo.lock stays, even if it is newer than the cooldown. The setting only affects which new versions the resolver may pick, so a bad version you already locked is still yours to find.
How do I install an urgent security fix during a cooldown?
Override it on purpose for that update. The Cargo docs describe setting resolver.incompatible-publish-age to allow, for example through CARGO_RESOLVER_INCOMPATIBLE_PUBLISH_AGE=allow, together with cargo update --precise for the one crate that needs the fix.
Would a cooldown have stopped the arrayref attack?
For a fresh resolve, a cooldown longer than 86 minutes would have skipped it. The Rust Security Response Team reports the malicious arrayref 0.3.10 was online for 86 minutes before deletion. It would not help a project that had already locked that version.
Is a dependency cooldown enough on its own?
No. The RFC that introduced it says the feature should not be relied upon for security by itself. Pair a cooldown with audits such as cargo vet, a reviewed Cargo.lock and advisory scanning.