chore(release): auto-create GitHub Release on tag publish#46
Merged
Conversation
Adds a github-release job to release.yml that runs after a successful npm publish and creates the matching GitHub Release with generated notes — prerelease-flagged for -suffixed versions, --latest for stable, mirroring the npm dist-tag split. Documents the automation in MAINTAINER.md and demotes manual gh release create to backfill/repair use only.
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.
What
Adds a
github-releasejob torelease.ymlthat runs after a successful npm publish and creates the matching GitHub Release with--generate-notes:*-*, e.g.-alpha.N) →--prerelease(excluded fromreleases/latest)--latestSame version-shape
casesplit the publish step already uses for npm dist-tags, so the two channels can never disagree. Job-scopedpermissions: contents: write; top-level permissions unchanged.Why
Release objects were previously created ad-hoc by hand — 16 of 22 tags had none, and gaps corrupt
--generate-noteswindows (it diffs against the previous Release object, not tag). History was backfilled and repaired 2026-07-24; this makes the ledger self-maintaining going forward.Docs
MAINTAINER.md §7/§8/§9 updated: automation documented, checklist gains a verify step, manual
gh release createdemoted to backfill/repair only.🤖 Generated with Claude Code