docs: update LTS versions and expand on policy
What changed, and why it matters
This commit only edits a documentation file describing which versions of the rust-bitcoin project are supported long-term. It removes detailed dependency tables and updates the list of maintained LTS branches. There is no code change and no security fix or vulnerability introduced.
No action needed; this is a routine documentation update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is limited to docs/supported-versions.md. It rewrites the supported-versions policy, drops the per-crate dependency version map, and now lists two v0.32 LTS branches (v0.32.10+ and v0.32.100+). No Rust source, build scripts, tests, or CI configuration were modified.
Changed components
docs/supported-versions.mdInspect captured patch +12 / −48
diff --git a/docs/supported-versions.md b/docs/supported-versions.md
index 3f6c49ac..71ab8210 100644
--- a/docs/supported-versions.md
+++ b/docs/supported-versions.md
@@ -1,14 +1,10 @@
-# Supported versions
+# Supported Versions
-List of crates, their versions that we still actively maintain, and the dependency versions.
+Three versions of the `bitcoin` crate are supported, the current in development version and two Long-Term Support (LTS) versions.
-## Bitcoin LTS versions
+Because the `bitcoin` crate is an umbrella across the rest of the crates in the workspace, the oldest LTS version's minimum dependencies determine the LTS versions of the other crates.
-- `v0.30` (Security and bug fixes only)
-- `v0.31` (Security and bug fixes only)
-- `v0.32`
-
-`v0.32` is the version most of the eccosystem is on. It is actively maintained. This means:
+LTS versions are actively maintained and receive updates like the following.
1. Will backport anything that is easy enough if requested and if possible within semver rules.
2. May attempt more involved backport work if we deem it important enough.
@@ -16,43 +12,11 @@ List of crates, their versions that we still actively maintain, and the dependen
4. Security and bug fixes, obviously.
(1) includes new features developed on `master`, so contributors are welcome to contribute a new
-feature with the explicit aim of then backporting it to `0.32`.
-
-## Dependency version map
-
-The LTS `bitcoin` releases and dependency versions (of crates in this repository).
-
-- `bitcoin 0.30`
- -> `bitcoin-private 0.1`
- -> `hashes 0.12`
-
-- `bitcoin 0.31`
- -> `internals 0.2`
- -> `hashes 0.13`
-
-- `bitcoin 0.32`
- -> `base58ck 0.1`
- -> `internals 0.3`
- -> `io 0.1`
- -> `units 0.1`
- -> `hashes 0.14`
-
-Currently in development:
-
-- `bitcoin 0.33-rc.x`
- -> `hashes 0.17`
- -> `io 0.2`
- -> `internals 0.4`
- -> `primitives-1.0.0-rc.x`
- -> `units-1.0.0-rc.x`
- -> (transitively `consensus-encoding 1.0.0-rc.x`)
-
-Once the RC cycle is done:
-
-- `bitcoin 0.33`
- -> `hashes 0.17`
- -> `io 0.2`
- -> `internals 0.4`
- -> `primitives-1.0.0`
- -> `units-1.0.0`
- -> `consensus-encoding 1.0.0`
+feature with the explicit aim of then backporting to LTS branches.
+
+## `bitcoin` LTS Versions
+
+- `v0.32.100+` -- MSRV of `1.60.0` and the optional `encoding` feature.
+- `v0.32.10+` -- MSRV of `1.56.1`.
+
+As of 2026-07-07, `v0.32` is the version most of the ecosystem is on and is actively maintained. Due to its longevity, we are in the unconventional spot of maintaining two branches of `v0.32` in an effort to make it easier for users to migrate to the stabilized crates.
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.