actions-marketplace-validations/Update Existing Release

Create, update, and edit existing releases! Great for creating a `latest` or `nightly` release.

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Maintainedlast commit Aug 6, 2025
License: None
Runtime: Deprecated runtime

Pinned Snippet

workflow.ymlSHA-pinned

uses: actions-marketplace-validations/isaacshelton_update-existing-release@5488e5b833eb42a743a8a2dbc3287092ac512ed0 # no releases — HEAD as of 2026-07-13

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
token	Your Github token; try \$\{\{ secrets.GITHUB_TOKEN \}\} if your build lasts less than an hour, or create your own secret token with repository access if your build requires longer than an hour.	yes	—
files	Paths to built files to be released. May be absolute or relative to \$\{\{ github.workspace \}\}.	yes	—
release	The name of the release to be created. A reasonable looking release name will be created from the current \$\{\{ github.ref \}\} if this input is not supplied.	no	—
tag	The name of the tag to be used. If not provided, the name of the release will be used.	no	—
message	A one-line description for both the tag and the release.	no	—
body	A fuller description of the release.	no	—
prerelease	Should the release, if created, be marked as a prerelease? Such releases are generally publicly visible.	—	false
draft	Should the release, if created, be marked as a draft? Such releases are generally not publicly visible.	—	false
replace	Should existing files for the release be removed if not overwritten?	—	false
updateTag	Should the tag be updated to point to the latest commit?	—	true

Outputs

name	description
files	The calculated path(s) to the files that were released.
draft	Whether the release, if created, was marked as a draft.
prerelease	Whether the release, if created, was marked as a prerelease.
release	The calculated human-friendly name of the release.
tag	The calculated tag for the release.