docs(release): prepare v0.16.1 recovery - #57
Merged
Merged
Conversation
Preserve the immutable v0.16.0 tag while aligning stable release metadata with the tag workflow and advancing the latest-release link.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
v0.16.0tag without moving itv0.16.1release notes with the exact stable-status line required by the tag workflowv0.16.0status line and advance the README latest-release link tov0.16.1Why v0.16.1
The
v0.16.0tag points to70d8930and remains immutable. Its release workflow stopped at the documentation gate because the checked-in status line included a date suffix.v0.16.1carries the same runtime behavior and public APIs while correcting the publication metadata safely.Verification
make ci-localStatus: **Released**releases/tag/v0.16.1unreleased v0.16.1markerRelease after merge
Create and push
v0.16.1, then require the full release workflow and tagged-consumer gates to pass before accepting the GitHub Release.Note
Low Risk
Documentation and release-metadata only; no runtime or API changes.
Overview
Prepares a v0.16.1 documentation-only recovery release so the stable-tag workflow can pass after
v0.16.0stalled on release metadata. Runtime behavior and public APIs are unchanged.The README latest published release link moves from v0.16.0 to v0.16.1. New
docs/release-notes/v0.16.1.mddocuments the recovery: keep the existingv0.16.0tag, use the exactStatus: **Released**line (no date suffix), and run full release gates before publishing GitHub Release.docs/release-notes/v0.16.0.mdis normalized to that same status format by removing the date suffix from the released line.Reviewed by Cursor Bugbot for commit 5aa3974. Bugbot is set up for automated code reviews on this repo. Configure here.