actions-marketplace-validations/Release Wizard
Create a Github release with parsed commits into a given Markdown template
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Mar 20, 2026
- License
- MIT
Pinned Snippet
uses: actions-marketplace-validations/darioblanco_release-wizard@a92158a297b008f8089a8c3b40bcf1ad7dcfa9dd # no releases — HEAD as of 2026-07-13tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| app | The name of the app involved in the release (monorepo mode). Creates tag and render commits for a specific scope, based on the given app name. Scopes from commits are analyzed for commits that follow the Angular commit style. e.g. `<type>(<app>): my commit title` or `(<app>): my commit title` | no | — |
| appTagSeparator | The separator for the tags if `app` is given. For example, if `@` is provided, the version calculated for such app will be based on `myapp@myversion`. Defaults to `/`, as it is common to see the `myapp/myversion` format. | no | / |
| baseTag | The tag that will be used as base for git commit comparison, instead of the automatic detection of latest published release. The commits will be formatted into a Markdown list and replaced into the `$CHANGES` variable for the given `templatePath` template file. | no | — |
| draft | Publish release draft | no | true |
| prerelease | Mark release as prerelease when creating | no | false |
| pushTag | Creates and pushes the automatic calculated tag before creating the release. Useful if you want the action to handle tags for you when publishing drafts. By default, a release draft won't create the tag, which only happens when it is published. | no | false |
| releaseName | The release title | no | — |
| releaseTitleTemplate | The release title template, ignored if releaseName is provided. | no | $TAG 🚀 |
| releaseTag | The git tag that will be linked to the release. If undefined, it will detect the latest tag and bump it. | no | — |
| taskBaseUrl | The base url to append for a detected task (do not set a trailing `/`). By default, it will create a url based on your Github organization. (e.g. https://myorg.atlassian.net/browse) | no | — |
| taskPrefix | The prefix that identifies task ids in the commits | no | JIRA- |
| templatePath | The path for the Markdown template that will be used to create the release body, relative to `.github/`. | no | release-wizard.md |
| token | The token to access Github's API | yes | — |
| withV | Prefix the calculated version with `v` | no | true |
Outputs
| name | description |
|---|---|
| change_type | The semantic type of change: major, minor, patch or prerelease |
| changes | A JSON array with the list of commit sha that are involved in the release |
| contributors | A JSON array with Github usernames of the people who contributed to the release |
| new_tag | The newly created tag that will reference the release |
| new_version | The newly created version that belongs to the tag |
| html_url | The browser url linking to Github's release |
| tasks | A JSON array with the list of project management tasks involved in the release |
| previous_tag | The previously detected tag that was bumped by the action |
| previous_version | The previously detected version that was bumped by the action |
| pull_requests | A JSON array with the list of Github pull requests involved in the release |
| release_id | The release id given by Github's API |
| upload_url | The url used for uploading release artifacts |