From 2ec6e27f8e8e0d37ce52552d1941fc04f1695612 Mon Sep 17 00:00:00 2001 From: Paul Hammant Date: Sun, 9 Aug 2026 20:04:46 +0100 Subject: [PATCH] docs(CHANGELOG): attribute fd_read_into to 0.510.0, which shipped it [skip actions] MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The 0.510.0 release left `## [current]` unrenamed, so VERSION said 0.510.0 while the newest heading was [current] — and the next release would have claimed fd_read_into as 0.511.0. Not a missing feature: release.yml:173-176 does the rename. It is a RACE. The release workflow branches from main when it starts, and: 19:38:05 feat(io): fd_read_into committed 20:02:45 #1476 merged to main 20:03:03 #1475 (release 0.510.0) merged <- 18 seconds later The release branch was cut before #1476 landed, so its `grep -q '## [current]'` correctly found nothing to rename — the backfill had just consumed the previous [current] and the new entry did not exist yet. The workflow behaved exactly as written; the window is the problem. This corrects the attribution only. The window itself is worth closing separately — see the follow-up issue. Co-Authored-By: Claude Opus 4.8 --- CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index dfb264cb0..c5ac49205 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -9,7 +9,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 `main`, the release pipeline automatically replaces `[current]` with the next version number before tagging the release. -## [current] +## [0.510.0] ### Added