Shipped · Databases

What etcd-io/etcd shipped

The public repository of Etcd · github.com/etcd-io/etcd

Written by FoxPlug from the repository's own releases; not affiliated with Etcd. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/etcd-io/etcd; Etcd did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

See the update FoxPlug writes for etcd, free

Week of November 2, 2026

What shipped

Why it matters

Two correctness fixes landed this week and were carried across the 3.5, 3.6 and 3.7 release branches: the alarmStore race and the force-new-cluster commit-index overshoot. For people running etcd, that means the fixes are available on the release lines they already use, and changelog entries were added so the changes are documented for upcoming patch releases.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: force-new-cluster no longer lets the adjusted commit-index exceed the last index, backported to 3.5, 3.6 and 3.7. alarmStore is now an atomic.Pointer to remove a race, also backported across all three release lines. Changelog entries added for both.

Post for LinkedIn

This week in etcd: force-new-cluster now prevents the adjusted commit-index from exceeding the last index. This matters after an unexpected crash, when the backend consistent_index can be ahead of the last WAL entry. The fix is backported to release-3.5, release-3.6 and release-3.7, with changelog entries added for v3.5.36, v3.6.17 and v3.7.4. alarmStore is now defined as an atomic.Pointer to avoid a race condition, and that change is backported across 3.5, 3.6 and 3.7 as well. The changelog was updated to cover the race issue.

Week of October 26, 2026

What shipped

Why it matters

This week the 3.5 release line received two correctness fixes: permission checks are no longer lost when a full database raises the NOSPACE alarm, and a leader that removed itself no longer serves a stale read index. Separately, the container base image was moved to distroless static-debian13 on the main and 3.5, 3.6 and 3.7 branches because older distroless images still trust compromised intermediate CAs with no patched release available.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: on release-3.5 the auth applier stays in the chain when the NOSPACE alarm fires, and a leader that removed itself no longer reads a stale index. The container base image moved to distroless static-debian13 on main and 3.5, 3.6 and 3.7: older distroless images trust com

Post for LinkedIn

This week in etcd: release-3.5 received two fixes. When the database becomes full and the NOSPACE alarm is raised, the request chain is rebuilt without the auth applier, which checks permissions; the applier is now kept. A leader that removed itself no longer uses a stale read index. On the packaging side, the Dockerfile base image moved to distroless static-debian13, backported to 3.5, 3.6 and 3.7, because the debian 11 and 12 distroless images still trust the compromised eMudhra intermediate CAs and have no patched release.

Week of October 19, 2026

What shipped

Why it matters

This week brings three patch releases on the 3.5, 3.6 and 3.7 lines, each with CHANGELOG and upgrade guidance for users moving up. Two concurrency fixes land in mvcc, one on main and backported to 3.6 and 3.5, and the build moves to Go versions carrying a CVE fix. A pty revert and a new session timeout option also reduce friction for people running tests and writing clients.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Etcd patch releases are out: v3.7.3, v3.6.16 and v3.5.35, each with updated CHANGELOG and upgrade guide. This week also fixes a data race in mvcc and moves the build to Go patch releases with a CVE fix.

Post for LinkedIn

Etcd v3.7.3, v3.6.16 and v3.5.35 are released this week, each with an updated CHANGELOG and upgrade guide, so check those before upgrading. The mvcc store had a data race between Hash and Restore, where the hash path read the backend and current revision without the locks the restore path holds; that is fixed on main and backported to 3.6 and 3.5. The build now uses Go patch releases that contain a CVE fix, and a revert of github.com/creack/pty to v1.1.18 addresses e2e CI failures running etcdctl. Clients also get a new session option to set a timeout for session creation.

Week of October 12, 2026

What shipped

Why it matters

This week lands a correctness fix for leader message ordering and a data race fix in keys-only RangeStream, both of which affect how the server handles streaming reads and replication traffic. The Go and dependency bumps, including x/net to v0.61.0 and otel to v1.45.0, address govulncheck failures and known vulnerability reports across the 3.5, 3.6 and 3.7 release lines. Test backports and a deflake also reduce noise for people running integration suites on the release branches.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: processMessages now keeps Ready message order, so MsgApp no longer goes out in reverse log order. Keys-only RangeStream data race fixed. Go 1.26.9 and x/net v0.61.0 bumps land on 3.5, 3.6 and 3.7. A flaky revision monotonic restart test was deflake.

Post for LinkedIn

This week in etcd: processMessages now preserves Ready message order, fixing a case where MsgApp left the leader in reverse log order and followers rejected messages whose previous index they did not have yet. The keys-only RangeStream data race is fixed by cloning the last key before appending a zero byte. Tests for processMessages output order landed on main and release-3.6, and the flaky revision monotonic leader restart test was deflake on release-3.7. Go moves to 1.26.9 and golang.org/x/net to v0.61.0 across 3.5, 3.6 and 3.7 to address govulncheck findings, with otel bumped to v1.45.0.

Week of October 5, 2026

What shipped

Why it matters

This week brings a panic fix for etcdctl lease comparisons back to the 3.6 release line and logs it in the changelog, so users comparing leases in transactions can upgrade without hitting the crash. The authentication commands now respect the global command timeout, which avoids indefinite hangs when the network is partitioned. The journal writer move also drops the systemd journal dependency from client consumers, while the deprecation and removal are documented across 3.7 and 3.8.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: etcdctl lease txn comparison fix backported to 3.6 and added to the changelog, auth CLI commands now honor the global command timeout, and the systemd journal log writer moved to server/embed so client consumers no longer carry that dependency.

Post for LinkedIn

This week in etcd: the etcdctl transaction comparison fix for leases was backported to release-3.6 and a v3.6.16 changelog entry was added, so lease comparisons no longer panic. User authentication CLI commands now apply the global --command-timeout instead of context.TODO(), which prevents long hangs during network partitions. The systemd journal log writer moved from client/pkg to server/embed, removing the systemd journal dependency from client consumers, and its deprecation and removal were recorded for 3.7 and 3.8. Tests also gained lease cases and a simpler channel receive in raft tests, plus the weekly dependency updates.

Week of September 21, 2026

What shipped

Why it matters

Three patch releases shipped across active versions with security updates addressing CVE-2026-84303 in gRPC. A new non-blocking defragmentation feature provides better availability during maintenance operations. Several bug fixes address resource leaks and improve operational tooling.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Etcd v3.7.2, v3.6.15, and v3.5.34 released. Security updates for CVE-2026-84303. New non-blocking defragmentation feature in v3.7.2.

Post for LinkedIn

Three etcd patch releases are available: v3.7.2, v3.6.15, and v3.5.34. These releases include security updates addressing CVE-2026-84303 in google.golang.org/grpc, critical for systems with gRPC dependencies. v3.7.2 introduces a new non-blocking defragmentation feature that allows defrag to run mostly in the background, minimizing service interruption. Bug fixes address resource leaks in WAL handling.

More from etcd-io/etcd on GitHub

Merged pull requests

Weeks with too little public activity are left out rather than filled in. Last updated 2026-11-09.

Is this your repo? Ask us to remove this page.