Repository navigation
chore(agent): changelog for v7.0.0 - #767
Merged
Merged
Conversation
Run scripts/gen-changelog.sh agent v7.0.0: render the v7.0.0 section of agent/CHANGELOG.md and promote agent/RELEASE_NOTES.md to the '## agent/v7.0.0' heading release.yml prepends to the release body. Lands on main first and is cherry-picked to release/agent/v7.0.x as the one bookkeeping commit between rc.2 and the final tag. Signed-off-by: Brian Lockwood <lockwobr@gmail.com>
github-actions
Bot
added
doc
6 tasks done
lockwobr
added a commit
that referenced
this pull request
Oct 5, 2026
Run scripts/gen-changelog.sh agent v7.0.0: render the v7.0.0 section of agent/CHANGELOG.md and promote agent/RELEASE_NOTES.md to the '## agent/v7.0.0' heading release.yml prepends to the release body. Lands on main first and is cherry-picked to release/agent/v7.0.x as the one bookkeeping commit between rc.2 and the final tag. (cherry picked from commit 0a542af) Signed-off-by: Brian Lockwood <lockwobr@gmail.com>
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.
Description
The changelog cut for
agent/v7.0.0, produced byscripts/gen-changelog.sh agent v7.0.0:agent/CHANGELOG.mdgains the## [agent/v7.0.0] - 2026-10-05section. The other changed lines in that file are the regenerated older sections losing trailing whitespace.agent/RELEASE_NOTES.mdgets the## agent/v7.0.0 - 2026-10-05heading under an empty## Unreleased, which is the headingrelease.ymlextracts the release body from.This lands on
mainfirst, matching the operator (58f8cc0e, "chore(operator): changelog for v0.19"), somaindoesn't keep the v7.0.0 notes under## Unreleasedafter the release ships. After merge it gets cherry-picked torelease/agent/v7.0.xas the one bookkeeping commit betweenagent/v7.0.0-rc.2and the final tag. Both files are currently identical onmainand the release branch, so the cherry-pick applies cleanly.Step 4 of Agent Releases says to run the cut on the agent branch, which contradicts the main-first rule. Not changed here; worth a follow-up.
How this was verified
Docs and generated changelog only; no code changed. Also ran the same cut on
release/agent/v7.0.xand compared the two: the only difference is thatmainlists #713 by its own title, where the branch would list the "Backport #708, #713 and #720" commit.AI assistance: produced with Claude Code.
Checklist
git commit -s -S.