Repository navigation
feat: workflow to replace the assets of an existing release - #98
Merged
Merged
Conversation
Re-publishes the installers from the share when the SDK is rebuilt under the same version, without regenerating the release. A required reason is appended to the release body under '## Asset Updates' with the date and the run link.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
.github/workflows/replace-release-assets.yml, aworkflow_dispatchwith inputstagand a requiredreasonrelease.yml, regenerate the body and put the release back into draft--strict, require the release notes PDF, show the checksum diff,gh release upload --clobber, delete assets the share no longer produces, lint the published names, re-download andsha256sum --check## Asset Updatesas- <date> - <reason> ([run](<url>)); existing text, title and draft state stay untouched[Unreleased]