Repository navigation
ci: trust the Knope draft tag - #5
Merged
Merged
Conversation
Knope created the v0.1.2 draft while bumping Cargo.toml to 0.1.1, so requiring the draft tag to equal Cargo.toml stalled the release for five minutes. Select the newest semver draft tag instead.
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.
Fixes the stalled v0.1.2 release.
Knope created a draft tagged
v0.1.2while updatingCargo.tomlto0.1.1(the release PR title preview wasRelease 0.1.2). The release workflow required the draft tag to equalCargo.toml, so it retried for five minutes and would fail.This selects the newest semantic-versioned draft tag as the release identity and builds from that tag. After merging, run
gh workflow run release.ymlto process the existingv0.1.2draft.