RepoJournal
Rust

@rust-lang

The Rust language, Cargo, and the standard library

Pick a date

  1. Wed 20 may
  2. Thu 21 may
  3. Sat 23 may
  4. Sun 24 may
  5. Mon 25 may
  6. Tue 26 may
  7. Wed 27 may
  8. Thu 28 may
  9. Fri 29 may
  10. Sat 30 may
  11. Sun 31 may
  12. Mon 1 jun
  13. Mon 8 jun
  14. Tue 9 jun
  15. Wed 10 jun
  16. Thu 11 jun
  17. Fri 12 jun
  18. Sat 13 jun
  19. Sun 14 jun
  20. Mon 15 jun
  21. Tue 16 jun
  22. Wed 17 jun
  23. Thu 18 jun
  24. Sat 27 jun
  25. Sun 28 jun
  26. Mon 29 jun
  27. Tue 30 jun
  28. Wed 1 jul
  29. Thu 2 jul
  30. Today 3 jul

The Wire · Showcase

CRATES.IO VENDORS CARGO-MANIFEST FOR FUTURE COMPATIBILITY

By RepoJournal · Filed · About Rust

The Rust package registry just made a strategic move to future-proof its Cargo.toml parsing by vendoring the upstream cargo-manifest crate directly into the workspace.

crates.io is now shipping with an embedded copy of cargo-manifest, rebranded as crates_io_cargo_toml, to stay aligned with evolving Cargo.toml specifications [1]. This matters because the published cargo-manifest crate parses the entire manifest spec, so every future change gets picked up immediately rather than chasing downstream updates. The integration required fixing snapshot metadata from the vendoring process [2], where insta tests were carrying workspace-relative paths that failed in CI. Alongside the infrastructure work, the Rust compiler's rollup landed 31 PRs including stabilization of core::range utilities and variance computation fixes [5], while the cargo submodule picked up 11 commits addressing refactoring and diagnostics improvements [6]. crates.io also bumped Node.js to v24.16.0 and typescript-eslint to v8.61.0 in routine maintenance [3], [4]. The dep-graph reverse index optimization landed in the compiler, replacing eager fingerprint-to-index maps with lazy per-DepKind construction for better startup performance [7].

Action items

References

  1. [1] Vendor `cargo-manifest` as `crates_io_cargo_toml` ↗ rust-lang/crates.io
  2. [2] cargo_toml: Fix snapshot metadata after vendoring rust-lang/crates.io
  3. [3] Update Node.js to v24.16.0 ↗ rust-lang/crates.io
  4. [4] Update typescript-eslint monorepo to v8.61.0 ↗ rust-lang/crates.io
  5. [5] Rollup of 31 pull requests ↗ rust-lang/rust
  6. [6] Auto merge of #157760 - weihanglo:update-cargo, r=weihanglo rust-lang/rust
  7. [7] Build the dep-graph reverse index lazily, per DepKind ↗ rust-lang/rust

FAQ

What changed in Rust on June 12, 2026?
The Rust package registry just made a strategic move to future-proof its Cargo.toml parsing by vendoring the upstream cargo-manifest crate directly into the workspace.
What should Rust teams do about it?
Review the cargo-manifest integration commits in crates.io PR#13910 - this is the strategic piece • Merge snapshot metadata fixes before next crates.io deploy • Watch the compiler rollup for stabilization impact on your MSRV
Which Rust repositories shipped on June 12, 2026?
rust-lang/crates.io, rust-lang/rust

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.