Bring gh-release entry fidelity up to commit-range bundling's - #3858
Open
cotti wants to merge 1 commit into
Open
Bring gh-release entry fidelity up to commit-range bundling's#3858cotti wants to merge 1 commit into
cotti wants to merge 1 commit into
Conversation
cotti
force-pushed
the
feature/gh-release-extraction-parity
branch
from
August 13, 2026 12:48
94420be to
e5a7527
Compare
gh-release mode produced title/link-only entries, a fidelity gap against the git-ref path (B5, #3775). It now follows the same ladder: a checked-in entry from the pool wins (matched by file-name-derived PR numbers or prs references, written verbatim so the curated content ships), otherwise release-note text from the PR body becomes the description and linked issues carry over, with title-only as the last resort. The bundle now selects exactly the files the run created — a PR-URL filter could never match pool entries whose prs references were scrubbed from public copies. Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
cotti
force-pushed
the
feature/gh-release-extraction-parity
branch
from
August 13, 2026 12:48
e5a7527 to
963d325
Compare
Mpdreamz
approved these changes
Aug 13, 2026
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
2 participants
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.
Why
gh-release mode produced title/link-only entries, a content-fidelity gap against commit-range bundling: products on the On-release GitHub Release path (APM agents, smaller repos) got lower-quality release notes than serverless products (RFC B5, closes #3775).
What
changelog gh-release(andchangelog add --release-version) now follows the same fidelity ladder as commit-range bundling for each PR in the release notes:prsreferences, and written verbatim so curated content ships. Pool unavailability degrades to synthesis with a warning, keeping repos that never upload entries working.changelog add, honoringextract.release_notes) and linked issues carry over (extract.issues).The bundle step now selects exactly the files the run created instead of filtering by PR URLs — pool entries whose
prsreferences were scrubbed from public copies could never match a URL filter. Reuses the pool-candidate matching from commit-range bundling (#3848).Stack: 5/5 (top).