Skip to content

ci(release): make GitHub-release job idempotent - #49

Merged
Liohtml merged 1 commit into
mainfrom
claude/project-analysis-crates-release-kqf0k9
Jul 17, 2026
Merged

ci(release): make GitHub-release job idempotent#49
Liohtml merged 1 commit into
mainfrom
claude/project-analysis-crates-release-kqf0k9

Conversation

@Liohtml

@Liohtml Liohtml commented Jul 17, 2026

Copy link
Copy Markdown
Owner

Follow-up to #48. The v0.3.0 tag run (29561730067) went: verify ✅, publish ✅ (skipped — 0.3.0 already on crates.io), create GitHub release ❌ with HTTP 422: Release.tag_name already exists, because the release had been created manually in the UI.

This makes the release-creation step skip when a release for the tag already exists — mirroring the idempotent publish step — so a manual UI release or a job re-run no longer fails the workflow.

No impact on v0.3.0 itself: the crate is published and the GitHub release exists; this only prevents the cosmetic red X on future tags.

🤖 Generated with Claude Code

https://claude.ai/code/session_01HHcB7Dhren7PSwn4va8BKv


Generated by Claude Code

Skip release creation when a release for the tag already exists (made
manually in the UI, or on a job re-run) instead of failing with
'Release.tag_name already exists' — mirrors the idempotent publish step.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HHcB7Dhren7PSwn4va8BKv
@coderabbitai

coderabbitai Bot commented Jul 17, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@Liohtml, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 18 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 87020b48-c5ca-4ad0-9a92-95a6a5ead3a9

📥 Commits

Reviewing files that changed from the base of the PR and between 0eb236f and 0948a79.

📒 Files selected for processing (1)
  • .github/workflows/release.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/project-analysis-crates-release-kqf0k9

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@Liohtml
Liohtml merged commit 66d1575 into main Jul 17, 2026
4 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.

2 participants