fix(release): trigger alpha publish pipeline - #632
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 51 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
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 |
skill-check — worker0 verified, 49 skipped (no docs/).
Four for four. Nicely done. |
* Revert "fix(release): trigger alpha tag publish (#633)" This reverts commit 45b212f. * Revert "fix(release): trigger alpha publish pipeline (#632)" This reverts commit 4f1b339. * Revert "fix(ci): simplify alpha release inputs (#628)" This reverts commit 72a6595. * Revert "feat(release): add alpha releases from pull request branches (#626)" This reverts commit ac0f750. * Revert "fix(release): isolate alpha releases (#631)" This reverts commit 156f5dd. * Revert "chore(image-resize): bump to v0.1.13-alpha.1" This reverts commit 0cba488. * Revert "feat(release): split version suffix from registry channel (#615)" This reverts commit d0bc06d.
What changed
Why
The workflow previously pushed tags with
GITHUB_TOKEN. GitHub does not start a second workflow from events created by that token, so the tag existed but the Release workflow never built or published it to the registry.Impact
Future alpha tags trigger Release, which builds the worker and publishes it to the
experimentalchannel.Validation
actionlint .github/workflows/alpha-release.ymlgit diff --check