Skip to content

fix: verify CI passed before tagging a release#92

Merged
reuvenharrison merged 2 commits intomainfrom
fix/release-check-ci
Apr 15, 2026
Merged

fix: verify CI passed before tagging a release#92
reuvenharrison merged 2 commits intomainfrom
fix/release-check-ci

Conversation

@reuvenharrison
Copy link
Copy Markdown
Contributor

Summary

  • release.sh now checks GitHub CI status on HEAD before creating the tag
  • Blocks the release if tests failed; prompts for confirmation if status is pending/unknown
  • Prevents releasing broken versions (like the v0.0.38 failure from the oasdiff v1.14.0 bump)

Test plan

  • Run ./release.sh when CI is green — should proceed normally
  • Run ./release.sh when CI is red — should block with error message

🤖 Generated with Claude Code

reuvenharrison and others added 2 commits April 12, 2026 15:40
release.sh now checks GitHub commit status and check-runs on HEAD
before creating the tag. Blocks the release if tests failed; prompts
if status is pending/unknown.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
When a repo uses only GitHub Actions (check-runs) and not commit
statuses, the status API returns "pending" by default. Checking
pending first would prompt unnecessarily even when all check-runs
passed. Check failure first so the pending branch only triggers
when status is genuinely unknown.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@reuvenharrison reuvenharrison force-pushed the fix/release-check-ci branch 3 times, most recently from 3d41ccd to ee78a59 Compare April 15, 2026 11:55
@reuvenharrison reuvenharrison merged commit 7939feb into main Apr 15, 2026
57 of 60 checks passed
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