actions-marketplace-validations/Semantic Release Notes Generator
Generates release notes using semantic-release/release-notes-generator
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Maintainedlast commit Jul 16, 2025
- License
- MIT
Pinned Snippet
uses: actions-marketplace-validations/fresa_release-notes-generator@a2a26e6bcca67f6960559c2ba86f8282518de3ce # no releases — HEAD as of 2026-07-10tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| version | The version of the release | yes | — |
| last_release_ref | The commit reference of the last release. The reference can be a tag, a branch or a commit sha. Examples: tags/v1.0.1 v1.0.1 heads/my-branch my-branch 431880b | yes | — |
| release_ref | The commit reference of this release. The reference can be a tag, a branch or a commit sha. Examples: tags/v2.0.0 v2.0.0 heads/master master 531c800 | yes | — |
| path_to_commits | The path to a file containing the commit messages and shas to parse as release notes. Example: ./commit-logs.json The content of the file should be formatted as a JSON list of commit message objects, example: [{"hash": "62c0a92ed8c684f966391c97ef68fcd7560ff666", "message": "This is a commit message"}] | yes | — |
| github_token | Authorized GitHub Access Token used to fetch the release notes generator. Defaults to github.token | no | ${{ github.token }} |
Outputs
| name | description |
|---|---|
| release_notes | Semantic release notes |