actions-marketplace-validations/Create/Update Github Release
An Action for creating and/or overwriting a GitHub release
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Nov 23, 2024
- License
- MIT
Pinned Snippet
uses: actions-marketplace-validations/mini-bomba_create-github-release@e84a2a34deaae6d7388de9171e4538721b570870 # no releases — HEAD as of 2026-07-10tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| token | Token used for creating/editing releases | yes | — |
| tag | Tag to create/move and use for the release | yes | — |
| target_commit | Commit, branch or tag the tag should be created from/moved to | no | — |
| prerelease | Should the release be marked as a prerelease? | no | — |
| draft | Should the release be marked as a draft? | no | — |
| name | Name of the release | no | — |
| body | Description of the release | no | — |
| files | Files to attach; newline seperated, recursive globbing supported | no | — |
| fail_on_no_files | Should the action fail if none of the file globs match? | no | false |
| clear_attachments | Should all existing attachments be deleted before uploading new files? | no | true |
| skip_tag_creation | Should the tag creation/modification be skipped? Set to true if the tag already exists and points to the correct commit | no | false |
Outputs
no outputs