fix: tolerate existing GH release so cargo-publish can run - #1783
Closed
danbugs wants to merge 1 commit into
Closed
Conversation
Signed-off-by: danbugs <danilochiarlone@gmail.com>
danbugs
requested review from
andreiltd,
dblnz,
devigned,
jprendes,
jsturtevant,
ludfjig,
simongdavies,
squillace and
syntactically
as code owners
August 28, 2026 17:13
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
1 participant
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.
Makes the
gh release createstep in CreateRelease.yml not fail when the release already exists. This allows re-triggering the full CreateRelease pipeline to publish crates via trusted publishing (which requires the OIDC token to come fromCreateRelease.yml, notCargoPublish.ymldirectly).This is needed because the v0.17.0 GitHub release was already created, but crate publishing failed due to the bug fixed in #1781.