@bleedingdev/modern-js-main-doc 3.5.0-ultramodern.17 → 3.5.0-ultramodern.19

package/docs/en/guides/get-started/ultramodern.mdx

@@ -78,6 +78,44 @@ mise exec -- pnpm check
 mise exec -- pnpm build
 ```
 
+### Migrating to `3.5.0-ultramodern.18`
+
+Use `3.5.0-ultramodern.18` or newer for localized Cloudflare SSR workspaces.
+This cohort moves bare locale-root redirects into the framework-owned
+Cloudflare Worker entry and the i18n server runtime. A request for `/` is
+redirected server-side with `302` to the negotiated locale path, for example
+`/cs` for `Accept-Language: cs-CZ` or `/en` for English and fallback traffic.
+
+Existing generated workspaces should upgrade the whole BleedingDev Modern
+package cohort together:
+
+```bash
+pnpm dlx @bleedingdev/modern-js-create@3.5.0-ultramodern.18 ultramodern \
+  migrate-strict-effect --version 3.5.0-ultramodern.18
+pnpm install
+pnpm check
+pnpm build
+pnpm cloudflare:build
+```
+
+For deployed Cloudflare Workers, redeploy after the cohort update and verify
+the root response before accepting the migration:
+
+```bash
+curl -I -H 'Accept-Language: cs-CZ,cs;q=0.9,en;q=0.1' https://<worker-host>/
+```
+
+The expected response is `302` with `Location: /cs` or the matching locale,
+`Cache-Control: private, no-store`, and `Vary` covering the locale detection
+headers. Following the redirect should return the SSR locale page with the
+matching document language and i18n SSR data.
+
+Do not fix older root `404` responses by adding app-owned root route files,
+client-side redirects, custom navigation wrappers, Cloudflare Worker
+postprocessing, generated output edits, or local redirect shims. If `/` still
+returns `404` after upgrading, confirm the production build log shows
+`Modern.js Framework v3.5.0-ultramodern.18` or newer and redeploy the Worker.
+
 Strict generated API migration requires `3.5.0-ultramodern.10` or newer.
 `3.4.0-ultramodern.20` and earlier cohorts do not include this full direct
 `api/index.ts` generator, generated `.mts` checks, strict Oxlint boundary rule

package/docs/zh/guides/get-started/ultramodern.mdx

@@ -71,6 +71,40 @@ mise exec -- pnpm check
 mise exec -- pnpm build
 ```
 
+### 迁移到 `3.5.0-ultramodern.18`
+
+本地化 Cloudflare SSR workspace 应使用 `3.5.0-ultramodern.18` 或更新版本。这个
+cohort 将裸 locale root 重定向移动到框架拥有的 Cloudflare Worker entry 和 i18n
+server runtime 中。请求 `/` 时，框架会按语言协商在服务端返回 `302`，例如
+`Accept-Language: cs-CZ` 会跳转到 `/cs`，英语或 fallback 流量会跳转到 `/en`。
+
+既有生成 workspace 应整体升级同一个 BleedingDev Modern package cohort：
+
+```bash
+pnpm dlx @bleedingdev/modern-js-create@3.5.0-ultramodern.18 ultramodern \
+  migrate-strict-effect --version 3.5.0-ultramodern.18
+pnpm install
+pnpm check
+pnpm build
+pnpm cloudflare:build
+```
+
+Cloudflare Workers 已部署环境需要在 cohort 更新后重新部署，并在接受迁移前验证 root
+响应：
+
+```bash
+curl -I -H 'Accept-Language: cs-CZ,cs;q=0.9,en;q=0.1' https://<worker-host>/
+```
+
+期望响应是 `302`，并带有 `Location: /cs` 或匹配的 locale、
+`Cache-Control: private, no-store`，以及覆盖语言检测 Header 的 `Vary`。继续跟随该
+redirect 后，应返回匹配语言的 SSR 页面，文档语言和 i18n SSR 数据也应一致。
+
+不要通过 app 自有 root route、客户端 redirect、自定义导航 wrapper、Cloudflare Worker
+postprocess、生成产物编辑或本地 redirect shim 来修复旧版本的 root `404`。如果升级后
+`/` 仍然返回 `404`，先确认生产构建日志显示
+`Modern.js Framework v3.5.0-ultramodern.18` 或更新版本，然后重新部署 Worker。
+
 严格生成 API 迁移要求 `3.5.0-ultramodern.10` 或更新版本。
 `3.4.0-ultramodern.20` 及更早 cohort 还没有这套完整的直接
 `api/index.ts` 生成器、生成的 `.mts` 检查、严格 Oxlint 边界规则、Effect 版本组

package/package.json

@@ -19,14 +19,14 @@
     "modern.js",
     "ultramodern.js"
   ],
-  "version": "3.5.0-ultramodern.17",
+  "version": "3.5.0-ultramodern.19",
   "publishConfig": {
     "registry": "https://registry.npmjs.org/",
     "access": "public"
   },
   "dependencies": {
     "mermaid": "^11.16.0",
-    "@modern-js/sandpack-react": "npm:@bleedingdev/modern-js-sandpack-react@3.5.0-ultramodern.17"
+    "@modern-js/sandpack-react": "npm:@bleedingdev/modern-js-sandpack-react@3.5.0-ultramodern.19"
   },
   "devDependencies": {
     "@rsbuild/plugin-sass": "2.0.0",