step-security/GH Release

Github Action for creating Github Releases

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
bodyNote-worthy description of changes in releaseno
body_pathPath to load note-worthy description of changes in release fromno
nameGives the release a custom name. Defaults to tag nameno
tag_nameGives a tag name. Defaults to github.ref_nameno
draftCreates a draft release. Defaults to falseno
prereleaseIdentify the release as a prerelease. Defaults to falseno
filesNewline-delimited list of path globs for asset files to uploadno
working_directoryBase directory to resolve 'files' globs against (defaults to job working-directory)no
overwrite_filesOverwrite existing files with the same name. Defaults to truenotrue
preserve_orderPreserve the order of the artifacts when uploadingno
concurrencyMaximum number of assets to upload in parallel. Ignored when preserve_order is true. Defaults to 4.no4
fail_on_unmatched_filesFails if any of the `files` globs match nothing. Defaults to falseno
fail_on_asset_upload_issueFails if any of the `files` fail to upload during the release. Defaults to falseno
repositoryRepository to make releases against, in <owner>/<repo> formatno
tokenAuthorized secret GitHub Personal Access Token. Defaults to github.tokenno${{ github.token }}
target_commitishCommitish value that determines where the Git tag is created from. Can be any branch or commit SHA.no
discussion_category_nameIf specified, a discussion of the specified category is created and linked to the release. The value must be a category that already exists in the repository. If there is already a discussion linked to the release, this parameter is ignored.no
generate_release_notesWhether to automatically generate the name and body for this release. If name is specified, the specified name will be used; otherwise, a name will be automatically generated. If body is specified, the body will be pre-pended to the automatically generated notes.no
previous_tagWhen generate_release_notes is true, use this tag as the starting point instead of letting GitHub auto-detect the previous release.no
append_bodyAppend to existing body instead of overwriting it. Default is false.no
make_latestSpecifies whether this release should be set as the latest release for the repository. Drafts and prereleases cannot be set as latest. Can be `true`, `false`, or `legacy`. Uses GitHub api default if not providedno
namedescription
urlURL to the Release HTML Page
idRelease ID
upload_urlURL for uploading assets to the release
assetsJSON array containing information about each uploaded asset, in the format given [here](https://docs.github.com/en/rest/reference/repos#upload-a-release-asset--code-samples) (minus the `uploader` field)