docs(changelog): cut the accumulated entries as the 0.0.1 release (FR-097) - #44
Avicennasis wants to merge 1 commit into
Conversation
…-097) The changelog had everything under [Unreleased] while a v0.0.1 GitHub release draft exists. Freeze the initial feature set as 0.0.1; [Unreleased] starts empty.
Avicennasis
left a comment
Avicennasis
left a comment
There was a problem hiding this comment.
The release metadata does not support cutting this section as 2026-05-08. v0.0.1 is still a draft (publishedAt: null) and no tag exists; May 8 is only the draft's creation date. More importantly, this change moves later work—such as the wipe USB added June 12 and the July documentation/fixes—under a May 8 release heading, creating an impossible changelog chronology.
Please either leave these entries under [Unreleased] until v0.0.1 is actually published, or date the section for the real release/cut and make sure it intentionally contains all work through that date. The draft itself should not be published as part of this PR; deployment/release steps are intentionally out of scope.
The Markdown diff itself is whitespace-clean and GitHub's current checks are green.
1 participant
Closes #48089. Freezes the accumulated
[Unreleased]content as[0.0.1] - 2026-05-08, matching the v0.0.1 GitHub release, leaving[Unreleased]empty.