Version bump from 0.15.0-rc.4: 57 replacements across 24 files, plus the CHANGELOG release section.
Every crate carries its version explicitly — there is no workspace.package.version — and the workspace dependency table and seven declared sibling dependencies repeat it, so a bump touches all of them. Cargo.lock is updated in the same commit.
The CHANGELOG's [Unreleased] section becomes ## [0.15.0-rc.5] - 2026-09-20, 160 entries, with its tree link.
Two things worth a look #
Three 0.15.0-rc.4 references are left on purpose. atproto-jetstream's README and MIGRATION.md name rc.4 as the last release that speaks Jetstream v1 (atproto-jetstream = "=0.15.0-rc.4"). That is a fact about that release, not a version to move — bumping it would point people at a release without v1.
The CI "path dependency version pins" step now covers all seven declarations. It checked three; it did not know about atproto-lexicon's two, atproto-repo's, or atpmcp's. Those four would have been left pointing at rc.4 — resolving to a stale published crate rather than the sibling path — which is the exact failure the step exists to catch. It now also asserts the count, so a declaration added later without a line there fails the build instead of waiting for the next release to expose it.
Verification #
cargo metadata reports one distinct version across all 19 packages. cargo fmt --all --check, cargo clippy --workspace --all-targets --all-features -- -D warnings, cargo test --workspace --no-fail-fast, and cargo check --workspace --all-targets -F clap,hickory-dns,zeroize,tokio,smtp are all clean. The pin check run locally reports all seven pins agreeing.