Skip to content

Release hotfix: set GH_REPO so gh release can find the repo#23

Merged
avrabe merged 1 commit into
mainfrom
hotfix/release-gh-repo-env
May 24, 2026
Merged

Release hotfix: set GH_REPO so gh release can find the repo#23
avrabe merged 1 commit into
mainfrom
hotfix/release-gh-repo-env

Conversation

@avrabe
Copy link
Copy Markdown
Contributor

@avrabe avrabe commented May 24, 2026

What broke

The v0.1.0 release run completed all the substantive work cleanly:

  • ✅ 4 cross-platform binary builds
  • ✅ CycloneDX SBOM
  • ✅ SHA256SUMS.txt
  • ✅ SLSA v1 build provenance (attestations recorded in Rekor)
  • ✅ Cosign keyless signature triple
  • ✅ build-env.txt
  • gh release create/upload:
failed to run git: fatal: not a git repository (or any of the parent directories): .git

Why

The wohl checkout lives at wohl/ (so the relay sibling can co-locate at ../relay). $GITHUB_WORKSPACE itself has no .git, so gh release view/create/upload can't infer the repo via the normal git remote lookup.

Fix

GH_REPO: ${{ github.repository }} in the step's env. One line, with a comment so the next person doesn't re-trip on it.

After merge

workflow_dispatch on the existing tag v0.1.0 re-runs everything. Each run gets fresh OIDC, fresh attestations, fresh cosign signatures — tied to the new run, not the failed one. Tag itself stays.

🤖 Generated with Claude Code

The v0.1.0 release run completed all the substantive steps — 4 binary
builds, SBOM, SHA256SUMS, SLSA build provenance, cosign keyless sig —
but the final "Create or update GitHub Release" step failed with:

    failed to run git: fatal: not a git repository (or any of the
    parent directories): .git

The wohl checkout lives at `wohl/` (so the relay sibling can co-locate
at `../relay`), so $GITHUB_WORKSPACE itself has no `.git`. `gh release
view/create/upload` falls back to a git remote lookup and errors out.
Setting `GH_REPO: ${{ github.repository }}` tells the gh CLI which
repo to act on without needing git context.

Re-running the workflow via workflow_dispatch on the existing tag
v0.1.0 will redo the full pipeline — fresh OIDC, fresh sigs, fresh
attestations — and upload everything. No retag needed.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@avrabe avrabe merged commit 27cb90f into main May 24, 2026
6 checks passed
@avrabe avrabe deleted the hotfix/release-gh-repo-env branch May 24, 2026 19:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant