ci: add auto-tag workflow missing from main#153
Conversation
The auto-tag.yml workflow was created during v0.9.0 development but wasn't included in the squash merge to main. Without it, release PRs merged to main don't trigger automatic tag creation, breaking the release pipeline (tag → build → publish → GitHub Release). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
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. Comment |
Summary
auto-tag.ymlworkflow that was created during v0.9.0 development but missed the squash merge to mainContext
The release pipeline chain is:
release/* PR merge → auto-tag creates vX.Y.Z → release.yml builds + publishesThis workflow was in
release/0.9.0but the squash merge of PR #149 didn't include it, so v0.9.0 never got tagged or released.After merge
Once this is on main, I'll manually create the
v0.9.0tag to trigger the release build.🤖 Generated with Claude Code