b1e90ff/Automated Release
Composite action that automates version management and changelog generation using semantic-release with conventional commits.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jun 8, 2026
- License
- MPL 2.0
Pinned Snippet
uses: b1e90ff/action-semantic-release@e44863d8d4b33a0e588f15cbf4e9f036a0ced8be # v1.2.1tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| github-token | Token for GitHub API access | yes | — |
| push-token | Token with write permissions for pushing release commits and tags (defaults to github-token) | no | "" |
| ref | Branch or tag to checkout | no | "" |
| dry-run | Preview mode - analyzes commits without creating a release | no | false |
| extra-plugins | Space or newline-separated list of additional semantic-release plugins to install | no | "" |
| node-version | Node.js runtime version | no | 24 |
| checkout-repository | Set to false if the repository is already checked out | no | true |
| npm-registry-scope | Scope for npm package registry authentication (e.g., @myorg) | no | "" |
| npm-registry-url | URL of the npm package registry | no | https://npm.pkg.github.com |
| enable-monorepo | Activate monorepo mode to release each module independently | no | false |
Outputs
| name | description |
|---|---|
| release_tag | Git tag created for the release (e.g., v1.2.3) |
| new_release_published | Indicates whether a new version was published |
| new_release_version | Semantic version number of the new release (e.g., 1.2.3) |
| release_type | Classification of the release (major, minor, patch) |