release: prepare v0.1.1249 RC for staging verification - #3965
Conversation
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 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 |
📦 Client bundle boundary
A server module in a client graph aborts hydration in the browser. New leaks fail CI; known leaks are tracked in |
Summary
0.1.1249-rcprerelease line so main publishes numbered RCs againWhy
0.1.1248is released and live in production. Whiledeno.jsonholds a cleanX.Y.Z, every pushto main re-enters the stable
releasejob rather than the prerelease publisher, so the next mergeswould have no RC to verify against staging. Moving to
0.1.1249-rcrestores the normalRC-then-promote cycle.
Verification
deno task generate:manifests:checkdeno task fmt:checkdeno test -A src/config/cicd-stable-release.test.ts src/utils/version.test.ts(
var VERSION = "0.1.1248"→"0.1.1249-rc")Released in production
Veryfront
0.1.1248shipped from559f04bae4:20260822063537-cfec7bdcc341(api#4475)20260822063031-849b6caab1a4(server#327)sha-df3b072520133c4dce5897dcf18518f5e36d5026-run-32557148908-attempt-1(job-runner#77)sha-f1c0781208d8f6d5f6cf9e8b4dfb709d6f4ee9cf-run-32557149043-attempt-1(sandbox#75)