Release v1.2.0

Summary

Prepares the publish workflows to move to the push trigger, which is what makes releases work for pull requests from forks.

Added

• reason output telling you why the action published nothing, so a workflow can fail on a release that went missing without failing on the ones that are expected.

Changed

• A commit that already has a release no longer publishes a second, higher version when its run is repeated (#103).
• Documented that cancel-in-progress: false is required under the push trigger.

Release v1.1.2

Added

• Documentation for the required contents: write permission, for choosing between the pull_request and push triggers (a push trigger keeps releases working for fork pull requests, whose token is read-only), and for manual workflow_dispatch runs.

Fixed

• A workflow_dispatch run left at the default 0.0.0 version no longer creates a bogus v0.0.0 release or publishes 0.0.0 artifacts. An empty or 0.0.0 version now works the version out from the merged pull request as intended.

Release v1.1.1

Summary

Release tags now ship only the files needed to run the action.

Changed

• Release tags (vX.Y.Z and the floating vX / vX.Y) now point at a lean commit containing only action.yml, dist, LICENSE and README.md, so a uses: checkout is about 2.7 MB instead of 6.6 MB.

Release v1.1.0

Summary

Closing a pull request without merging it no longer creates a GitHub release.

Added

• major-labels, minor-labels and patch-labels inputs to configure which label names drive each version bump.
• tag-prefix input to configure the prefix used for the release tag.
• tag and previous-version outputs.
• 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 version without release-notes now 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-request output was inverted and now reports correctly.
• Releases now point at the actual merge commit instead of the ephemeral pull-request merge commit.