fix(ci): extract full release notes from CHANGELOG#118
Merged
Conversation
The regex lookahead `\n#+\s` matched any heading level (##, ###, ####), so the lazy capture group stopped at the first `### Bug Fixes` subsection and returned an empty string. Narrow the lookahead to `\n## ` so it only stops at h2 version boundaries. Co-Authored-By: Claude Opus 4.6 <[email protected]>
Contributor
Vulnerability Scan: PassedImage: No vulnerabilities found. Commit: 1d180b8 |
ltucker
approved these changes
Apr 21, 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.
Two fixes for the release workflow pipeline:
Release notes extraction — the regex stopped at the first
###subsection heading instead of the next##version heading, producing an empty body on the v1.1.0 GitHub Release. Narrows the lookahead to match only version headings.Lockfile sync —
semantic-releasebumps the version inpyproject.tomlbut the release PR didn't regenerateuv.lock, breaking the Docker build on merge. Addsuv lockafter the version bump and includesuv.lockin the PR paths.v1.1.0 release notes have been backfilled separately.
Test plan
uv.lockand Docker build passes