agilecustoms/Generate release
Generate next release version and notes
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jun 24, 2026
- License
- MIT
Pinned Snippet
uses: agilecustoms/release-gen@b89e3a7231fa6f1588d8667a4e553937438bd820 # v4.2.13tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| changelog_file | CHANGELOG.md file path. Pass empty string to disable changelog generation | no | CHANGELOG.md |
| changelog_title | Title of the changelog file (first line of the file) | no | — |
| floating_tags | When next version to be released is 1.2.4, then also release 1, 1.2 and latest. Not desired for public terraform modules | no | — |
| notes_tmp_file | Temporary file to store release notes | no | /tmp/release-gen-notes |
| release_branches | The branches on which releases should happen. It will override the branches attribute in your configuration file | no | — |
| release_channel | Basically a tag that moves on each release, primarily used with with input `version` | no | — |
| release_plugins | Release plugins configuration | no | — |
| tag_format | Tag format. Default: v${version} | no | — |
| version | Explicit version to use instead of auto-generation | no | — |
| version_bump | Allows to bump a version w/o semantic commits | no | — |
Outputs
| name | description |
|---|---|
| channel | Release channel such as latest (for main branch), next (for prerelease) or support (for maintenance) |
| version | The next release version generated by the action based on commits since last release tag |
| git_tags | Space-separated git tags to create |
| notes_tmp_file | Equal to corresponding input, just for convenience |
| prerelease | Whether the release is a prerelease or not |
| tags | Space-separated tags to create: git_tags + branch name |