From 0ba3ea0f0ad7f69906959e5dd9b06b55e8e86491 Mon Sep 17 00:00:00 2001 From: RobertoIskandarani Date: Mon, 31 Aug 2026 12:02:28 -0300 Subject: [PATCH] docs: move the unreleased entries out of the 0.1.0 section Two changelog changes landed on main in the same session and interleaved badly: one recorded the 0.1.0 section to match the tag, the other added its own entries at the top of the file. The result was a duplicate `## [0.1.0] - 2026-08-07` heading, with 247 lines of unreleased work filed underneath it and the real `[Unreleased]` section left empty. So main claimed 0.1.0 shipped resource-identifier validation, inbound DPoP nonce enforcement and the pinned conformance catalog. None of that is in the v0.1.0 tag or in the published 0.1.0 package, both of which predate the work by three weeks. Drop the duplicate heading so those entries fall under `[Unreleased]` where they belong. The surviving `## [0.1.0]` section is byte-identical to the one at the tag, verified by comparison rather than by eye. --- CHANGELOG.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 5106591..f671370 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,8 +7,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ## [Unreleased] -## [0.1.0] - 2026-08-07 - ### Added - Resource-server-side DPoP nonce enforcement (RFC 9449 ยง9). Until now the