Create manual workflow to generate releases #221
Merged
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.
Overview
I was thinking about how we could do releases with fewer clicks and still automating the release notes, so I've built a manual workflow.
Here's how it works:
Releasefrom the left-hand panelRun workflowbuttonVersion bump type (_patch_, _minor_, or _major_), which will be used innpm versionWhen you run the workflow, it will:
npm versionto bump the package.json and package-lock.json, but we use--no-git-tag-versionbecause it prefixes with avand we don't want that for this projectvghcommand) to get a list of PR titles so we don't need all the "by @dependabot" textHere's an example from my repo: