chore: release v1.25.0-beta.8 - #2341
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📥 CommitsReviewing files that changed from the base of the PR and between 1f34281 and 0f45477274cf92ed3a1a751aa7e233d5d62057e1. ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (4)
Included review availability: Your plan provides up to 8 included reviews per hour; 1 remains after this review. 📝 SummarySummary by CodeRabbit
WalkthroughThe release version was updated from ChangesRelease version alignment
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: Merge Risk: ⚪ Minimal · up to This change only advances release metadata to v1.25.0-beta.8, with the supplied files showing consistent versions across Python, frontend, and Helm. No merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 Generate unit tests (beta)
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 |
fe2cf33 to
13b1b9d
Compare
a250d2f to
92161dc
Compare
Live upstream/account smoke — run against production after deployRecorded here as promised in the release-candidate validation checklist: the live smoke could not bind to the candidate SHA before merge because the image did not exist yet, so it was run against production immediately after Deploy: blue/green cutover on Health, 80 minutes post-cutover: 5,961 success / 47 error / 12 cancelled. The errors are Scheduled sweep, on real data: End-to-end functional smoke — a real thread through the front door, on a hard
The durable row now names the replacement account with both retirement markers NULL — the rebinding claim cleared the marker, so retirement is a step rather than a resting state. Account A was restored to Before this train that third request returned 502 |
Summary
Changes since v1.25.0-beta.7
1f3428)
c52941)
6d11e5)
d6a7ca)
478e96)
e04005)
08f963)
195b33)
9cfce7)
8e5760)
04a309)
53253c)
aa75e1)
94fb4d)
c9d544)
4096c1)
9368d4)
21eedb)
e32f85)
6b3d03)
92c7f6)
98d225)
09b8e8)
53f968)
7f7929)
976d20)
c62bdd)
a096b6)
9db05a)
cb21da)
b04b27)
2c8539)
3d9027)
cc25f2)
ef7010)
b36e5a)
63314a)
10cd71)
883c91)
2852cf)
d28b3a)
Release-candidate validation
Validated candidate: 0041600
Complete these checks on the exact candidate SHA above before merging. The beta release guard and publish workflow fail while any item remains unchecked or the SHA is stale.
Tests (pytest, unit),integration-core-1..3,integration-bridge,e2e,PostgreSQL, plusMigration check (alembic)andMigration check (alembic, PostgreSQL)— all pass.Frontend tests (vitest + coverage),Frontend build (vite),Frontend type check (tsc),Frontend lint (eslint)— all pass.Package (build)passes.Docker build,Helm lint + template + kubeconformandHelm smoke install (kind)pass;Dashboard browser smoke (Playwright)also passes against the built dashboard.1.25.0-beta.8, and the result is reported back on this PR. 39 of 40 checks on this SHA are green; the only red one is this guard.Install after publish
uvx --from "codex-lb==1.25.0b8" codex-lb docker pull ghcr.io/Soju06/codex-lb:1.25.0-beta.8 helm install codex-lb oci://ghcr.io/soju06/charts/codex-lb --version 1.25.0-beta.8 --develPromotion
Merge the normal release-please PR to promote this beta-tested train to 1.25.0.