ci: add GitHub release creation to publish workflow#77
Open
Conversation
After npm publish, the workflow now extracts release notes from CHANGELOG.md and creates a GitHub release using gh CLI. Changes: - Bump contents permission from read to write - Add changelog extraction step using awk - Add gh release create step with --verify-tag - Add release URL to verify step output
iamfj
force-pushed
the
feat/publish-github-release
branch
from
fe31cdd to
bf8e645
Compare
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.
Summary
After publishing to npm, the publish workflow now automatically creates a GitHub release with release notes extracted from
CHANGELOG.md, matching the format of previous releases (e.g. v2025.12.3, v2025.12.2).Changes
contentspermission:read→write(required forgh release create)awk[version]: urlreference link###headings to##(CHANGELOG nests under## [version], releases use top-level##)---separators and collapses blank lines**Full Changelog**: <compare-url>headergh release createwith--verify-tagand the extracted notesContext
v2026.4.1 was published to npm but no GitHub release was created. The existing v2026.4.1 release has been manually fixed to match the format of previous releases. This PR ensures all future tag-triggered publishes create a correctly formatted GitHub release automatically.
Testing