Skip to content

docs(changelog): retitle Unreleased to 0.13.0 (released 2026-07-30) - #61

Open
mavaali wants to merge 1 commit into
mainfrom
chore/changelog-0.13.0
Open

docs(changelog): retitle Unreleased to 0.13.0 (released 2026-07-30)#61
mavaali wants to merge 1 commit into
mainfrom
chore/changelog-0.13.0

Conversation

@mavaali

@mavaali mavaali commented Aug 2, 2026

Copy link
Copy Markdown
Owner

Release commit bf97990 (chore: release v0.13.0, #58) bumped pyproject.toml to 0.13.0 but never retitled the ## [Unreleased] section in CHANGELOG.md, leaving all 0.13.0-era entries under Unreleased.

This retitles the section to ## [0.13.0] - 2026-07-30 (the release date of bf97990) and adds a fresh empty ## [Unreleased] above it, matching the file's Keep a Changelog conventions. CHANGELOG.md is unchanged since bf97990, so every entry in the section belongs to 0.13.0 — no post-release entries needed to stay under Unreleased.

Resolves the changelog finding from the nightly maintenance sweep in #60.

🤖 Generated with Claude Code

Release commit bf97990 bumped pyproject.toml to 0.13.0 but left the
changelog entries under [Unreleased]. Retitle the section to
[0.13.0] - 2026-07-30 and add a fresh empty [Unreleased] above it.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@claude

claude Bot commented Aug 2, 2026

Copy link
Copy Markdown

Reviewed for correctness against the invariants in GUIDE.md / docs/boundary-contract-spec.md (write allowlist/floor/ceiling, staging pivot, spend-fails-closed, Third Umpire grading, selftest coverage, red-team tests, core-vs-overlay boundary) — none of those apply here, this PR only retitles ## [Unreleased] to ## [0.13.0] - 2026-07-30 in CHANGELOG.md.

  • Change is a correct, minimal 2-line diff matching Keep a Changelog conventions; pyproject.toml is already at 0.13.0, consistent with the new heading.
  • No code, tests, or enforcement logic touched, so no selftest/red-team coverage is needed.
  • Pre-existing: the version reference-link list at the bottom of CHANGELOG.md hasn't been maintained past [0.5.0] (no [0.13.0]: .../releases/tag/v0.13.0 link), but that gap predates this PR and is out of scope for a retitle-only change.

No correctness, simplification, or efficiency findings. LGTM.

@claude claude Bot mentioned this pull request Aug 3, 2026
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