@bleedingdev/modern-js-main-doc 3.5.0-ultramodern.1 → 3.5.0-ultramodern.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/docs/en/configure/app/bff/effect.mdx +10 -4
  2. package/docs/en/guides/get-started/ultramodern.mdx +15 -10
  3. package/docs/zh/configure/app/bff/effect.mdx +10 -4
  4. package/docs/zh/guides/get-started/ultramodern.mdx +13 -9
  5. package/package.json +7 -7
package/docs/en/configure/app/bff/effect.mdx CHANGED
@@ -197,18 +197,24 @@ The generated `api.client.*` API only exists for loader-materialized `@api/index
197
197
  ## Effect cohort
198
198
 
199
199
  UltraModern-generated workspaces pin the framework-compatible Effect cohort
200
- through `pnpm-workspace.yaml` overrides. For `3.5.0-ultramodern.1`, generated
200
+ through `pnpm-workspace.yaml` overrides. For `3.5.0-ultramodern.3`, generated
201
201
  apps use:
202
202
 
203
203
  ```yaml
204
+ trustPolicyExclude:
205
+ - '@effect/opentelemetry@4.0.0-beta.91'
206
+
204
207
  overrides:
205
- '@effect/vitest': 4.0.0-beta.89
206
- effect: 4.0.0-beta.89
208
+ '@effect/vitest': 4.0.0-beta.91
209
+ effect: 4.0.0-beta.91
207
210
  ```
208
211
 
209
212
  Do not add a different direct `effect` version in an app package. A mismatched
210
213
  Effect beta can fail while building layers or HTTP middleware because runtime
211
- services come from different package instances.
214
+ services come from different package instances. Keep the generated
215
+ `trustPolicyExclude` entry with the same Effect cohort; it handles the
216
+ `@effect/opentelemetry` trusted-publisher to provenance metadata transition
217
+ without weakening UltraModern API architecture checks.
212
218
 
213
219
  ## Contract tests
214
220
 
package/docs/en/guides/get-started/ultramodern.mdx CHANGED
@@ -78,33 +78,38 @@ mise exec -- pnpm check
78
78
  mise exec -- pnpm build
79
79
  ```
80
80
 
81
- Strict generated API migration requires `3.5.0-ultramodern.1` or newer.
81
+ Strict generated API migration requires `3.5.0-ultramodern.3` or newer.
82
82
  `3.4.0-ultramodern.20` and earlier cohorts do not include this full direct
83
83
  `api/index.ts` generator, generated `.mts` checks, strict Oxlint boundary rule
84
84
  set, Effect cohort overrides, and strict Effect migration command. Agents that
85
85
  cannot install that BleedingDev cohort yet should use the local Modern.js
86
- workspace for migration validation; otherwise pin `3.5.0-ultramodern.1` or
86
+ workspace for migration validation; otherwise pin `3.5.0-ultramodern.3` or
87
87
  newer with `--ultramodern-package-version`.
88
88
 
89
89
  Before hand-editing package aliases or generated metadata, run the framework
90
90
  migration command from the target workspace:
91
91
 
92
92
  ```bash
93
- pnpm dlx @bleedingdev/modern-js-create@3.5.0-ultramodern.1 ultramodern \
94
- migrate-strict-effect --version 3.5.0-ultramodern.1
93
+ pnpm dlx @bleedingdev/modern-js-create@3.5.0-ultramodern.3 ultramodern \
94
+ migrate-strict-effect --version 3.5.0-ultramodern.3
95
95
  pnpm api:check
96
96
  pnpm contract:check
97
97
  ```
98
98
 
99
99
  The command updates `.modernjs/ultramodern.json`, root
100
- `modernjs.packageSource`, generated Modern package aliases, direct topology API
101
- metadata, and the pnpm lockfile. Remaining failures are source migration work:
102
- move code to `shared/api.ts`, `api/index.ts`, and `src/api/*-client.ts`, then
103
- delete `api/effect`, `api/lambda`, `shared/effect`, and `src/effect`.
100
+ `modernjs.packageSource`, generated Modern package aliases, framework-owned
101
+ toolchain pins, direct topology API metadata, strict Effect pnpm
102
+ overrides/trust policy, and the pnpm lockfile. Remaining failures are source
103
+ migration work: move code to `shared/api.ts`, `api/index.ts`, and
104
+ `src/api/*-client.ts`, then delete `api/effect`, `api/lambda`, `shared/effect`,
105
+ and `src/effect`.
104
106
 
105
107
  Generated strict Effect workspaces pin the compatible Effect cohort with pnpm
106
- overrides: `effect@4.0.0-beta.89` and `@effect/vitest@4.0.0-beta.89`. Do not
107
- add app-local direct Effect versions that disagree with those overrides.
108
+ overrides: `effect@4.0.0-beta.91` and `@effect/vitest@4.0.0-beta.91`. Do not
109
+ add app-local direct Effect versions that disagree with those overrides. They
110
+ also carry a generated pnpm trust-policy exclusion for
111
+ `@effect/opentelemetry@4.0.0-beta.91` so pnpm no-downgrade checks do not block
112
+ the Effect beta cohort's trusted-publisher to provenance metadata transition.
108
113
 
109
114
  Gradual migration means old, unmigrated Modern.js apps can keep their existing
110
115
  runtime until they are converted. Once a surface is generated or migrated as
package/docs/zh/configure/app/bff/effect.mdx CHANGED
@@ -195,16 +195,22 @@ export default defineConfig({
195
195
  ## Effect 版本组
196
196
 
197
197
  UltraModern 生成的 workspace 会通过 `pnpm-workspace.yaml` overrides 锁定与框架兼容的
198
- Effect 版本组。`3.5.0-ultramodern.1` 使用：
198
+ Effect 版本组。`3.5.0-ultramodern.3` 使用：
199
199
 
200
200
  ```yaml
201
+ trustPolicyExclude:
202
+ - '@effect/opentelemetry@4.0.0-beta.91'
203
+
201
204
  overrides:
202
- '@effect/vitest': 4.0.0-beta.89
203
- effect: 4.0.0-beta.89
205
+ '@effect/vitest': 4.0.0-beta.91
206
+ effect: 4.0.0-beta.91
204
207
  ```
205
208
 
206
209
  不要在应用包里添加不同版本的直接 `effect` 依赖。Effect beta 不一致时，Layer 或 HTTP
207
- middleware 构建可能因为运行时 service 来自不同包实例而失败。
210
+ middleware 构建可能因为运行时 service 来自不同包实例而失败。保留生成的
211
+ `trustPolicyExclude` 条目并让它跟随同一个 Effect 版本组；它用于处理
212
+ `@effect/opentelemetry` 从 trusted-publisher metadata 迁移到 provenance attestation
213
+ 时的 pnpm no-downgrade 检查。
208
214
 
209
215
  ## 契约测试
210
216
 
package/docs/zh/guides/get-started/ultramodern.mdx CHANGED
@@ -71,30 +71,34 @@ mise exec -- pnpm check
71
71
  mise exec -- pnpm build
72
72
  ```
73
73
 
74
- 严格生成 API 迁移要求 `3.5.0-ultramodern.1` 或更新版本。
74
+ 严格生成 API 迁移要求 `3.5.0-ultramodern.3` 或更新版本。
75
75
  `3.4.0-ultramodern.20` 及更早 cohort 还没有这套完整的直接
76
76
  `api/index.ts` 生成器、生成的 `.mts` 检查、严格 Oxlint 边界规则、Effect 版本组
77
77
  overrides 和严格 Effect 迁移命令。还不能安装该 BleedingDev cohort 的 agent 应使用本地
78
78
  Modern.js workspace 做迁移校验；否则用 `--ultramodern-package-version` 固定
79
- `3.5.0-ultramodern.1` 或更新版本。
79
+ `3.5.0-ultramodern.3` 或更新版本。
80
80
 
81
81
  手写 package alias 或生成 metadata 之前，先在目标 workspace 运行框架迁移命令：
82
82
 
83
83
  ```bash
84
- pnpm dlx @bleedingdev/modern-js-create@3.5.0-ultramodern.1 ultramodern \
85
- migrate-strict-effect --version 3.5.0-ultramodern.1
84
+ pnpm dlx @bleedingdev/modern-js-create@3.5.0-ultramodern.3 ultramodern \
85
+ migrate-strict-effect --version 3.5.0-ultramodern.3
86
86
  pnpm api:check
87
87
  pnpm contract:check
88
88
  ```
89
89
 
90
90
  该命令会更新 `.modernjs/ultramodern.json`、根 `modernjs.packageSource`、生成的
91
- Modern package alias、直接 topology API metadata 和 pnpm lockfile。剩余失败就是源码迁移：
92
- 把代码移到 `shared/api.ts`、`api/index.ts` 和 `src/api/*-client.ts`，再删除
93
- `api/effect`、`api/lambda`、`shared/effect` 和 `src/effect`。
91
+ Modern package alias、框架拥有的 toolchain pin、直接 topology API metadata、严格 Effect
92
+ pnpm overrides/trust policy 和 pnpm lockfile。剩余失败就是源码迁移：把代码移到
93
+ `shared/api.ts`、`api/index.ts` 和 `src/api/*-client.ts`，再删除 `api/effect`、
94
+ `api/lambda`、`shared/effect` 和 `src/effect`。
94
95
 
95
96
  严格 Effect 生成 workspace 会通过 pnpm overrides 固定兼容版本组：
96
- `effect@4.0.0-beta.89` 和 `@effect/vitest@4.0.0-beta.89`。不要添加与这些
97
- overrides 冲突的 app 本地直接 Effect 版本。
97
+ `effect@4.0.0-beta.91` 和 `@effect/vitest@4.0.0-beta.91`。不要添加与这些
98
+ overrides 冲突的 app 本地直接 Effect 版本。生成的 pnpm policy 还会为
99
+ `@effect/opentelemetry@4.0.0-beta.91` 添加 trust-policy exclusion，避免 Effect beta
100
+ 版本组从 trusted-publisher metadata 迁移到 provenance attestation 时被 pnpm
101
+ no-downgrade 检查误拦截。
98
102
 
99
103
  渐进迁移意味着尚未迁移的旧 Modern.js app 可以保留现有 runtime，直到被转换为
100
104
  UltraModern。一个 surface 一旦生成为或迁移为 UltraModern HTTP API，就只能使用
package/package.json CHANGED
@@ -19,24 +19,24 @@
19
19
  "modern.js",
20
20
  "ultramodern.js"
21
21
  ],
22
- "version": "3.5.0-ultramodern.1",
22
+ "version": "3.5.0-ultramodern.3",
23
23
  "publishConfig": {
24
24
  "registry": "https://registry.npmjs.org/",
25
25
  "access": "public"
26
26
  },
27
27
  "dependencies": {
28
- "mermaid": "^11.15.0",
29
- "@modern-js/sandpack-react": "npm:@bleedingdev/modern-js-sandpack-react@3.5.0-ultramodern.1"
28
+ "mermaid": "^11.16.0",
29
+ "@modern-js/sandpack-react": "npm:@bleedingdev/modern-js-sandpack-react@3.5.0-ultramodern.3"
30
30
  },
31
31
  "devDependencies": {
32
32
  "@rsbuild/plugin-sass": "2.0.0",
33
- "@rspress/core": "2.0.14",
34
- "@rspress/plugin-llms": "2.0.14",
35
- "@rspress/shared": "2.0.14",
33
+ "@rspress/core": "2.0.15",
34
+ "@rspress/plugin-llms": "2.0.15",
35
+ "@rspress/shared": "2.0.15",
36
36
  "@shikijs/transformers": "^4.3.0",
37
37
  "@types/fs-extra": "11.0.4",
38
38
  "@types/node": "^26.0.1",
39
- "@typescript/native-preview": "7.0.0-dev.20260624.1",
39
+ "@typescript/native-preview": "7.0.0-dev.20260628.1",
40
40
  "classnames": "^2.5.1",
41
41
  "clsx": "^2.1.1",
42
42
  "fs-extra": "^11.3.5",