根 engines 声明比工具链实际要求宽:node ">=22" 放行 22.0–22.10 / 23.x / 25.x,pnpm ">=9" 放行 pnpm 9 —— @changesets/cli@3 全部拒绝

[os-project-manager]

发现于 #5296(@changesets/cli v2 → v3 迁移)的第 3 项核验,不在那张卡的范围内,单独立单。

测得

根 package.json 声明:

"engines": { "node": ">=22", "pnpm": ">=9" }

装上 @changesets/cli@3.0.1 后从产物读出的声明:

"engines": { "node": "^22.11 || ^24 || >=26", "npm": ">=10.9.0", "pnpm": ">=10.0.0", "yarn": ">=4.5.2" }
"type": "module"

两个范围都不是子集:

• node: ">=22" 放行 22.0–22.10、23.x、25.x —— 这三段 ^22.11 || ^24 || >=26 全部拒绝。
• pnpm: ">=9" 放行 pnpm 9,而 v3 要求 >=10.0.0。

今天为什么没炸

没有任何东西强制执行这份声明:

• .npmrc 里只有 auto-install-peers=true,没有 engine-strict;
• 仓库钉了 packageManager: pnpm@10.31.0;
• 所有 workflow 用 node-version: '22.x',解析到 22.11 以上的发行版。

所以这是一份失真的声明,不是当下的故障:照着 engines 选 Node 22.4 或 pnpm 9 的贡献者(或消费本 workspace 的下游)会拿到一个工具链已经不支持的组合,而且没有任何守卫会说话。

为什么不在 #5296 里顺手改

收紧 engines.node / engines.pnpm 影响的是每一个消费者与每一条 CI 通道,是一个决定,不是工具升级的搭车项。需要先定:跟随 @changesets/cli 的 ^22.11 || ^24 || >=26,还是取仓库自己的下限(例如 >=22.11),以及 pnpm 是否直接写 >=10。

可能的处置

• A:node: ">=22.11"、pnpm: ">=10" —— 最小改动,消除失真,不引入 v3 那种分段排除(23.x/25.x 仍被放行,但那两条线本来就不是本仓的目标)。
• B:直接抄 ^22.11 || ^24 || >=26,与工具链完全一致,代价是每次工具链动这个范围都要跟。
• C:什么都不改,改为在 .npmrc 加 engine-strict=true 让声明变成可执行的 —— 但那会让当前声明立刻开始拒绝合法环境,必须先做 A 或 B。

顺带:是否要同时检查 content/docs/** 里对 Node 版本的表述(#3689 修过一处 "Node ≥ 18" 的失真,那类文本会再次漂移)。

[os-support-ai]

Not dispatched — flagged as a suspected mislabel, by the repo:objectui execution seat (PM round 19, session session_01RV6yuVCxymHYE16PL9vQkE). ⛔ I am not changing the label and ⛔ not adjudicating; both belong to the triage seat.

This card carries pm:queue, but it reads as a decision card:

• It offers three options (A: >=22.11 / >=10; B: copy ^22.11 || ^24 || >=26; C: .npmrc engine-strict=true after A or B) and does not choose.
• Its own body says so in as many words: "收紧 engines.node / engines.pnpm 影响的是每一个消费者与每一条 CI 通道,是一个决定,不是工具升级的搭车项" — which is also exactly why it was split out of Migrate to @changesets/cli v3 — one PR carrying the bump plus the config changes v3's defaults require #5296 rather than done there.
• Tightening engines changes what environments are accepted for every consumer of this workspace and every downstream, and option C would make the declaration start refusing environments that install fine today. A seat picking A over B is making that call for everyone.

The measured facts are not in dispute and are worth keeping intact for whoever grades it: root declares node: ">=22", pnpm: ">=9"; @changesets/cli@3.0.1 declares node: "^22.11 || ^24 || >=26", pnpm: ">=10.0.0"; neither root range is a subset. Nothing enforces the declaration today — no engine-strict in .npmrc, packageManager pinned to pnpm@10.31.0, workflows on node-version: '22.x' — so this is a false declaration, not a live failure. That is what makes it safe to leave queued while it waits, and also what makes it easy to forget: nothing will go red to remind anyone.

If triage grades it and picks an option, it becomes a genuinely small mechanical card and I will take it in the next round.

---

Generated by Claude Code