Fix final GitHub Release publication step - #12
Merged
Conversation
MuteJester
marked this pull request as ready for review
July 18, 2026 13:16
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.
What changed
Pass the explicit repository to
gh release editin the final release job.Root cause
The job has no checkout step, so
ghcould not infer a repository and failed after PyPI and GHCR had already succeeded. The v3.0.0 draft was published manually with the same explicit repository target.Validation
gh release edit v3.0.0 --repo MuteJester/AlignAIR --draft=false --latestsuccessfully published the release