Fix release notes fetching from stale master branch#262
Merged
Conversation
…anch The release-notes-tool repo's default branch is main, but the workflow was curling from master — a stale branch still containing the broken sed pattern that truncates changelog entries at = characters. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.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
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.
Summary
release-notes-toolfrommaininstead ofmastermasterbranch is stale and still has the broken sed pattern that truncates changelog entries containing=charactersProblem
The 1.8.8 GitHub Release only contained 2 of 8 changelog entries. The fix to the sed pattern (bmlt-enabled/release-notes-tool#2) was merged to
main, but this workflow was curling frommaster.Test plan
🤖 Generated with Claude Code