Merged
Conversation
Expose the bumped package versions from the publish job and add a parallel 'create-release' job that creates one GitHub Release per published package. The job is matrixed across packages, checks whether each package was published via the publish.outputs.versions, checks prerelease status, checks out the package tag, prefers a per-package CHANGELOG entry for release notes (falls back to generated notes), and creates the appropriate release (stable with changelog, stable with auto notes, or prerelease). Also grants contents write permission and gates execution on dry-run/custom version inputs.
There was a problem hiding this comment.
Pull request overview
This PR extends the existing Publish Package GitHub Actions workflow to expose the per-package versions computed during publishing and then create one GitHub Release per published package tag via a parallel matrix job.
Changes:
- Expose
publishjob outputversionsfrom the version bump step. - Add a
create-releasematrix job that, per package, detects whether it was published and then creates the appropriate GitHub Release (stable w/ changelog, stable w/ auto notes, or prerelease).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| : > "$out" | ||
| if [ -f "$file" ]; then | ||
| awk -v v="## [$ver]" ' | ||
| $0 ~ "^" v { flag=1; print; next } |
Replace the regex-based ^v match with index($0, prefix) == 1 when locating the version header in the release notes. This ensures a literal prefix match (avoiding regex metacharacter issues) and more reliably extracts the section for the given version.
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.
Expose the bumped package versions from the publish job and add a parallel 'create-release' job that creates one GitHub Release per published package. The job is matrixed across packages, checks whether each package was published via the publish.outputs.versions, checks prerelease status, checks out the package tag, prefers a per-package CHANGELOG entry for release notes (falls back to generated notes), and creates the appropriate release (stable with changelog, stable with auto notes, or prerelease). Also grants contents write permission and gates execution on dry-run/custom version inputs.