chore: release v0.51.0 - #323
Conversation
|
👀 Quinn is reviewing — verdict (PASS / WARN / FAIL) + findings to follow. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (6)
WalkthroughAll package manifests across the monorepo are updated from version 0.50.0 to 0.51.0. The root and CLI package configurations also update the sandbox Docker image URI from ChangesRelease Version 0.51.0
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
QA Audit — PR #323 | chore: release v0.51.0
VERDICT: PENDING — CI not yet terminal
CI Status
- CodeQL: in_progress
- Lint: in_progress
Diff Review
Automated minor version bump: 0.50.0 → 0.51.0 across root package.json, package-lock.json, and all 5 workspace packages (cli, core, test-utils, web-templates, webui). Also updates sandboxImageUri tags in root and packages/cli. No logic changes — pure version bump.
Observations
- MEDIUM: Headless version-bump PRs typically warrant a pre-approved/auto-merge label in the repo's CI policy to avoid unnecessary review latency. This is a process note for maintainers, not a blocker here.
- Everything else is routine and low-risk.
Formal PASS/FAIL verdict will be issued once CI completes.
— Quinn, QA Engineer
|
Submitted COMMENT review on #323 — CI is still in progress (CodeQL + Lint both |
Code Coverage Summary
CLI Package - Full Text ReportCore Package - Full Text ReportFor detailed HTML reports, please see the 'coverage-reports-22.x-ubuntu-latest' artifact from the main CI run. |
…ersion (#325) When several PRs merge in quick succession, each CI completion triggers auto-release.yml. They ran concurrently, each computed the same next version from the same last tag, and each opened a bump PR (e.g. #323 and #324 both "chore: release v0.51.0"). One release.yml run published; the other hit the already-tagged guard and exited 1 — a spurious red ❌ on an otherwise-clean release. - auto-release.yml: serialize with `concurrency: auto-release` and, before opening the bump PR, skip if `v$VERSION` is already tagged or an `auto-release/v$VERSION` branch already exists (the queued run now observes what the earlier run created). - release.yml: the already-tagged path is an expected no-op, not an error — warn and exit 0 instead of exit 1 so a duplicate-PR re-trigger isn't red. Co-authored-by: Automaker <automaker@localhost> Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
Automated version bump to v0.51.0 (minor).
Summary by CodeRabbit