Release v1.1.0
Summary
Closing a pull request without merging it no longer creates a GitHub release.
Added
major-labels,minor-labelsandpatch-labelsinputs to configure which label names drive each version bump.tag-prefixinput to configure the prefix used for the release tag.tagandprevious-versionoutputs.- A decision table written to the job summary explaining what the run decided.
Changed
- The action now runs on Node 24.
- The action now honors
GITHUB_API_URL, so it runs on GitHub Enterprise Server. - A release created without notes of its own now uses GitHub's generated release notes instead of an empty body.
- An explicit
versionwithoutrelease-notesnow creates a release instead of being skipped.
Fixed
- A pull request closed without being merged no longer produces a release, even when it has a release label (#2, #4).
- Duplicate releases from the version being recalculated in the post step are no longer created (#103).
- A merged pull request from a branch named after a version now produces a correct version.
- The
isolated-for-pull-requestoutput was inverted and now reports correctly. - Releases now point at the actual merge commit instead of the ephemeral pull-request merge commit.