Skip to content

fix(ci): use version tag instead of branch ref when publishing CLI binaries#2803

Open
robert-hebel-sb wants to merge 1 commit into
masterfrom
fix/release-binary-publish-tag
Open

fix(ci): use version tag instead of branch ref when publishing CLI binaries#2803
robert-hebel-sb wants to merge 1 commit into
masterfrom
fix/release-binary-publish-tag

Conversation

@robert-hebel-sb
Copy link
Copy Markdown
Contributor

Summary

  • ghr was being called with ${{ github.ref }} (refs/heads/master) as the release tag in the Build & publish CLI binaries job
  • Lerna creates the GitHub release under a semver tag (e.g. v5.15.11), so ghr failed with release is not found (exit code 11)
  • Fix: resolve the tag via git describe --tags --abbrev=0 after checkout and use git rev-list -n 1 $TAG for the correct commitish

Test plan

  • Trigger a release workflow and confirm the Build & publish CLI binaries job passes
  • Verify CLI binaries are attached to the correct GitHub release tag

Fixes failed run: https://github.com/stoplightio/prism/actions/runs/26869475559/job/79241795766

🤖 Generated with Claude Code

…naries

ghr was called with \${{ github.ref }} (refs/heads/master) as the release
tag, causing it to fail with "release is not found" since the GitHub
release created by lerna is associated with the semver tag (e.g. v5.15.11),
not the branch name.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@robert-hebel-sb robert-hebel-sb requested a review from a team as a code owner June 3, 2026 07:35
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