feat: add automated release workflows#46
Merged
Conversation
Adds a manually-triggered "Prepare release" workflow that bumps all version-bearing files (root/dashboard/report-action package.json + lockfiles, README action-usage pins) and writes the CHANGELOG.md entry from conventional-commit history, then opens a PR. Since main is ruleset-protected, a second "Publish release" workflow tags the merge commit and creates the GitHub Release automatically once that PR merges.
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
release-prepare.yml: manualworkflow_dispatch(version input) that bumps all version-bearing files (root/dashboard/.github/actions/reportpackage.json+ lockfiles, README action-usage pins), generates the CHANGELOG.md entry from conventional-commit history since the last tag, and opens arelease/vX.Y.ZPR againstmain.release-publish.yml: triggers on merge of arelease/v*PR, tags the merge commit, and creates the GitHub Release using the just-merged CHANGELOG.md section as notes.mainis ruleset-protected, so a direct-push single-workflow design isn't possible — merging the release PR is the approval gate, and publishing then happens automatically.Test plan
generate-changelog-entry.mjsagainst real repo history (categorizesfix/feat/etc., skipsdocs/chore/test/ci/build/style)insert-changelog-entry.mjssplices the new section + link ref above the existing CHANGELOG.md entryextract-changelog-section.mjscorrectly bounds a section by the next heading or the trailing link-reference blocknpm version --no-git-tag-versionbumps package.json + package-lock.json without needingnode_modules.github/actions/report@vX.Y.Zpin replacement (caught and fixed a bug where the pattern assumed a lowercase org prefix)release-prepare.ymlend-to-end against a real version bump once merged🤖 Generated with Claude Code