changelog: compile v6.2.0 fragments ahead of the tag - #141
Conversation
…oject-estimation) Mechanical changelog compilation (build-changelog.py) ahead of the v6.2.0 tag — sole diff is the generated CHANGELOG.md [Unreleased] region. cut_release.py refuses to tag while CHANGELOG.md is out of sync with changelog.d/ fragments. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
You have reached your Codex usage limits for security reviews. Please try again later. |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 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. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ef3443ce7b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| alongside the coordinator fault-tolerance client changes and the | ||
| `project-estimation` skill. | ||
|
|
||
| ### agent-collab 6.2.0 - 2026-08-21 |
There was a problem hiding this comment.
When the inspected release.yml publishes v6.2.0, it invokes extract_changelog_section.py, whose first-match logic stops at this second ### agent-collab heading. Running that extractor against this commit returns only the runtime 4.1.0 entry, so the coordinator changes—including the fix for #125—and the project-estimation section are omitted from the GitHub Release notes even though they ship in v6.2.0. Consolidate these entries beneath one v6.2.0 heading, or update the generator/extractor before compiling, so the published evidence describes the complete release.
AGENTS.md reference: AGENTS.md:L44-L48
Useful? React with 👍 / 👎.
1 participant
Summary
Mechanical changelog compilation (
build-changelog.py) ahead of the v6.2.0 tag. Sole diff is the generatedCHANGELOG.md[Unreleased]region (102 fragments compiled, including the dual-arch runtime 4.1.0 fragment, the coordinator fault-tolerance fragment, and project-estimation).cut_release.pyrefuses to tag whileCHANGELOG.mdis out of sync withchangelog.d/fragments.Testing
build-changelog.py --check→ IN SYNC after the compile.CHANGELOG.md(verified viagit status --porcelain).Compliance trace
author: claude
standing_directives: directive #3 (release process), #5 (release docs), #6 (Tier-1 self-merge), operational-reliability baseline
tier: 1
cross_check: N/A (Tier 1 — deterministic mechanical compilation of existing changelog fragments; the generated CHANGELOG.md is reproducible via build-changelog.py and gated by build-changelog.py --check in CI).
post_condition: after merge, cut_release.py's changelog gate passes; the v6.2.0 signed tag is cut (operator-gated) and release.yml compiles the versioned release notes from this section.
mcp_coverage_gap: NONE
contributor_rights: OPERATOR-CONFIRMED
operator_reserved: no — mechanical changelog compilation is routine release-cycle completion (the subsequent tag/publish is the operator-gated step).