Use release-action for GitHub release publishing#136
Merged
Conversation
webup
added a commit
that referenced
this pull request
May 14, 2026
PR #136 replaced the custom release-notes.mjs script with ncipollo/release-action's generateReleaseNotes, which relies on PR labels that nobody applies — resulting in empty release notes. Restore the script that parses conventional commit prefixes (feat, fix, etc.) directly from git log, groups them into Features & Polish / Fixes / Misc buckets with collapsible details, and appends a Contributors section with first-time contributor welcome. Wire it into the publish-release job: preface + script output → RELEASE_BODY.md, replacing generateReleaseNotes.
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
Switch release publishing to
ncipollo/release-action@v1so GitHub generates the changelog, new contributor acknowledgements, full changelog link, and contributor avatar section. The workflow now keeps ClawMaster-specific install and desktop download instructions as a custom release preface before the generated notes.Why
This uses GitHub's standard release-note machinery for contributor acknowledgement while preserving the project-specific installation content we need at the top of each release.
How
RELEASE_PREFACE.mdwith CLI, npm, desktop installer, and checksum links.gh releasecreate/edit/upload calls withncipollo/release-action@v1using generated notes, artifact replacement, prerelease, draft, and latest controls.Screenshots
Not applicable; this PR only changes release automation.
Related Issue
Closes #135
Type of Change
Testing
npm testpasses locallyjs-yamlv0.3.1resolvesprevious_tag=v0.3.0console.logor debug artifacts left in codeDependency Changes
Checklist
feat/,fix/,chore/,docs/,test/,ci/)