Skip to content

docs: backfill CHANGELOG v0.23.0/v0.23.1 + restore 3 shipped-tag release-notes files - #393

Merged
100yenadmin merged 2 commits into
mainfrom
docs/rc3-changelog-notes-backfill
Aug 27, 2026
Merged

100yenadmin merged 2 commits into
mainfrom
docs/rc3-changelog-notes-backfill

Conversation

@100yenadmin

Copy link
Copy Markdown
Member

Summary

Pre-rc3 release-history hygiene (2026-08-27 audit findings):

  • CHANGELOG.md: main jumped ## v0.23.2 → ## v0.23.0-rc1, missing the two SHIPPED stable releases. Backfilled ## v0.23.1 - 2026-08-23 and ## v0.23.0 - 2026-08-22, sourced from their release-notes content, matching the file's compact-bullet style.
  • Restored 3 notes files absent from main but present (and published) at their tags — verbatim via git show <tag>:.github/release-notes/<tag>.md: v0.23.0-rc2.md, v0.23.1-rc1.md, v0.23.1.md.

Change class

Docs-only (CHANGELOG + .github/release-notes/) = routine risk class; carry-forward-safe under RELEASE-READINESS-V1 §4. Ordered BEFORE the v0.23.2-rc3 tag so the rc tree carries complete history and GA remains a pure notes addition.

Verification

  • tests/test_release_workflow.py green (8 passed) — CHANGELOG identity assertions hold.
  • Notes files byte-identical to their tagged versions (mechanical git show restoration, no hand edits).
  • Chronology check: grep '^## v' CHANGELOG.md now strictly descending.

…-tag notes files

The CHANGELOG on main jumped v0.23.2 -> v0.23.0-rc1, skipping the two shipped
stable releases (v0.23.0 final 2026-08-22, v0.23.1 privacy release 2026-08-23);
and three notes files that shipped at their tags (v0.23.0-rc2, v0.23.1-rc1,
v0.23.1 — each published by release.yml from the tagged tree) are absent from
main. Backfill both from the tags' own release-notes content (notes files
restored VERBATIM via git show <tag>:...).

Docs-only (carry-forward-safe per RELEASE-READINESS-V1 §4); lands before the
v0.23.2-rc3 tag so the rc3 tree carries the full release history and the GA
delta stays a pure notes addition. Found by the 2026-08-27 work-so-far audit.
@coderabbitai

coderabbitai Bot commented Aug 27, 2026 •

Copy link
Copy Markdown

Warning

Review limit reached

Next included review available in 54 minutes.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 25566b8a-c87f-4c4f-8f80-3dca95b437d6

📥 Commits

Reviewing files that changed from the base of the PR and between c0402f3 and 6d43810.

📒 Files selected for processing (5)
  • .github/release-notes/v0.23.0-rc2.md
  • .github/release-notes/v0.23.0.md
  • .github/release-notes/v0.23.1-rc1.md
  • .github/release-notes/v0.23.1.md
  • CHANGELOG.md

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

…me class)

The #393 adversarial review's full-repo drift sweep found in-tree v0.23.0.md
was the ONLY remaining notes file drifting from its published tag (missing the
'Stable promotion...' preamble + the #325 bullet; still carrying an older
rc1-flavored line). Restored verbatim via git show v0.23.0:... — the same
mechanical operation as the other three. Every notes file now matches its tag.
@100yenadmin
100yenadmin merged commit 73a2c0e into main Aug 27, 2026
15 checks passed
@100yenadmin
100yenadmin deleted the docs/rc3-changelog-notes-backfill branch August 27, 2026 09:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant