chore: release v1.23.0-beta.5

[Soju06]

Summary

• Prepares beta release v1.23.0-beta.5 for the 1.23.0 stable train.
• Updates release-managed version files only; release-please remains the stable release owner.
• Merging this PR will publish v1.23.0-beta.5 only after the release-candidate validation checklist below is completed for this exact candidate SHA.
• Synced automatically from release-please PR chore(main): release 1.23.0 #1472; no manual beta workflow dispatch is required.

Changes since v1.23.0-beta.4

• feat(auth): enable Auth Guardian by default and cover paused accounts (feat(auth): enable Auth Guardian by default and cover paused accounts #1662) (ebb0525)
• fix(db): keep api-key reservation accounting at full durability (fix(db): keep api-key reservation accounting at full durability #1665) (
  5b81f2)
• fix(usage): keep the covering read path effective on append-heavy usage_history (fix(usage): keep the covering read path effective on append-heavy usage_history #1666) (

• fix(api-keys): make the shutdown flush of last_used_at coalescing lossless (fix(api-keys): make the shutdown flush of last_used_at coalescing lossless #1667) (
  0fcb6a)
• fix(auth): keep guardian candidates session-safe (fix(auth): keep guardian candidates session-safe #1669) (
  ff2920)
• fix(proxy): never inject a cross-account previous_response_id anchor (takeover of fix(proxy): never inject a cross-account previous_response_id anchor #1274) (fix(proxy): never inject a cross-account previous_response_id anchor (takeover of #1274) #1638) (

• fix(proxy): detect stalled upstream websockets (fix(proxy): detect stalled upstream websockets #1579) (
  a0a977)
• fix(proxy): fail over stuck HTTP bridge owner requests to a fresh account (fix(proxy): fail over stuck HTTP bridge owner requests to a fresh account #1401) (
  f2f8f9)
• fix(proxy): complete Codex compaction SSE lifecycle (fix(proxy): complete Codex compaction SSE lifecycle #1634) (
  7f91b9)
• fix(proxy): recover dead durable bridge anchors fast (fix(proxy): recover dead durable bridge anchors fast #1625) (
  85f1ee)

Release-candidate validation

Validated candidate: fe1ba41

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.

• Backend/unit/integration gates — CI green at fe1ba41 (unit, integration-core 1-3 + required, integration-bridge, PostgreSQL, migration checks sqlite+postgres; all non-guard checks success)
• Frontend tests/build — CI green at fe1ba41 (frontend lint/typecheck/tests/build, dashboard browser smoke)
• Wheel/package validation — CI Package (build) green at fe1ba41 (sdist/wheel build + verify)
• Docker/container smoke — image built locally from fe1ba41 (sha256:150a1ead1385); booted against a scratch postgres:18-alpine: alembic migrated an empty DB to head 20260806_120000_add_http_bridge_owner_process_epoch (54 tables; conversation presence satellite present; usage_history autovacuum reloptions codified as insert_scale_factor=0.02/insert_threshold=50000/analyze_scale_factor=0.02), / 200, /api/runtime/version and /v1/models 401 (auth enforced), 0 error signatures in logs
• Live upstream/account smoke
• Live upstream/account smoke not required — this beta deploys to the production pool immediately after publish for the release-channel soak; live-path verification happens there with the rollback runbook staged (deploy.sh cutover records tag+revision; the schema delta since beta.4 is additive — one state column via the bridge owner-epoch migration and reloption tuning — with tested downgrades)

Install after publish

uvx --from "codex-lb==1.23.0b5" codex-lb
docker pull ghcr.io/Soju06/codex-lb:1.23.0-beta.5
helm install codex-lb oci://ghcr.io/soju06/charts/codex-lb --version 1.23.0-beta.5 --devel

Promotion

Merge the normal release-please PR to promote this beta-tested train to 1.23.0.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.