fix: pass --repo to gh release edit in publish-release job - #17
Merged
Conversation
The publish-release job has no checkout step, so gh CLI cannot infer the target repository from git context: failed to run git: fatal: not a git repository (or any of the parent directories): .git This was the third and final blocker in the release pipeline (after #15's npm ci fix and #16's Quint install fix). v0.2.7 was manually published via 'gh release edit' after confirming all its artifacts (Go/Rust/TS binaries+archive, 6 SBOMs, Cosign signatures, public GHCR images) were already valid. This fix ensures the *next* release (v0.2.8+) auto-publishes without manual intervention.
This was referenced Aug 18, 2026
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.
Problem
After #15 and #16 fixed
npm ciand the missing Quint install, the Release pipeline ran end-to-end for the first time —release-verify,version, and all threerelease-{go,rust,ts}jobs succeeded, producing a fully valid v0.2.7 draft (binaries, TS archive, 6 SBOMs, Cosign-signed public GHCR images). Only the finalpublish-releasejob failed:The job has no
actions/checkoutstep, soghcan't infer which repository to target.Fix
Pass
--repo "${{ github.repository }}"explicitly instead of adding an unnecessary checkout step.Verification
gh release edit v0.2.7 --draft=false --prerelease=false) after independently verifying its artifacts:cosign verify-able against therelease.yml/push/refs/heads/mainOIDC identityPart of epic #4; completes #8 pipeline validation once verified on the next release.