[objectstack-fleet]

Requested by Yibo Wang · project thread

Fixes #29957

维护者速读

• 改了什么: 18.3 发布页在「需手动处理 › Metadata the build, lint and save doors now refuse」下补一条：fix(lint)!: publish refuses a text-vs-number comparison in a validation rule (or another fail-closed predicate) instead of warning, then refusing every write #29923 的收窄（失败即拒的谓词里文本/布尔字段和数字比大小，18.2.0 发布时只给 warning、之后拒掉每次写入 → 18.3.0 在发布时直接拒），写明它实际发出的 type-mismatch + params.outcome: 'fail-closed'，以及 main 上 fix(lint)!: a type mismatch in a record-triggered flow condition or an advisory validation rule is served a verdict that says what really happens #29953 已把它改名为 type-mismatch-fail-closed。docs/releases-maintenance.md 加三步编号的发版顺序：合并 Version Packages PR 前列出 main 在其分叉点之后新增的 changeset 并刷新；发布后确认版本提交留下的 pending changeset 为零，不为零就写进发布页。
• 为什么改: chore: version packages #26517 13:39Z 从 40a35ded 生成后，14:44Z 合并时没有再刷新，落后 main 5 次合入，4 个 changeset（其中 1 个是破坏性的 fix(lint)!: publish refuses a text-vs-number comparison in a validation rule (or another fail-closed predicate) instead of warning, then refusing every write #29923）的代码进了 18.3.0，但 CHANGELOG 没有它们。发布页的「Release facts」里已经点名了这 4 个，但破坏性那条不在需手动处理列表里，也没写出实际的拒绝码。
• 风险与回滚: 只改两份文档，无代码、无 changeset、无 workflow 改动。没有加守卫：scripts/release-pending-publish.mjs 里 release(next): 18.0.0-next.2 shipped 11 changesets with no CHANGELOG entry (the version PR merged behind main; #21361's class, in pre mode) #23818 已测量过 main 约每 20 分钟一次带 changeset 的合入，拒绝过期 PR 的检查几乎会拦住每次发版，所以选运行手册步骤。回滚 = revert。
• 先看: content/docs/releases/v18/18-3.mdx 新增的那条（约第 283 行起），以及 docs/releases-maintenance.md 的「The cut, in order」三步。
• 两分钟验证: 在完整 clone 上跑 node scripts/release-pending-publish.mjs unconsumed --version-commit 83d7e4ae --version 18.3.0，预期列出 4 个 changeset；第 1 步的命令换成 git merge-base 72d7db03 b1c4119e（chore: version packages #26517 的 head）后同样列出这 4 个文件。
• 需要你做的: 无，席位审阅落地（文档 PR，skip-changeset）。

Clause-②: no
Metadata-protocol: none

What changes

• content/docs/releases/v18/18-3.mdx. Under 需手动处理 › Metadata the build, lint and save doors now refuse, the count line now says "8 entries, and one more that 18.3.0 ships with no entry in its CHANGELOGs", followed by a bullet for fix(lint)!: publish refuses a text-vs-number comparison in a validation rule (or another fail-closed predicate) instead of warning, then refusing every write #29923: the sites (validation rule condition / when, requiredWhen, readonlyWhen, option visibleWhen, hook condition), the before and after (18.2.0 published with an expression-invalid warning and then refused every write it could not evaluate; 18.3.0 refuses at os validate, os build, the object save door and publish at severity: error), the refusal it carries (type-mismatch with params.outcome: 'fail-closed', the same on MCP validate_expression for site: 'validation'), the remedy, the upgrade-guide entry validation-type-mismatch-refused, and that main serves it as type-mismatch-fail-closed since fix(lint)!: a type mismatch in a record-triggered flow condition or an advisory validation rule is served a verdict that says what really happens #29953. The Release facts note that already named the four leaked changesets now points to that bullet. The counts the page takes from the CHANGELOGs (8, 264, 1,379) are unchanged, because the entry is not in them.
• docs/releases-maintenance.md. Cutting a GA release gains "The cut, in order": (1) list the changesets main gained since the Version Packages PR's branch point, with the command, and refresh until the list is empty; (2) the existing wait for a nearer CI run; (3) confirm the version commit left zero changesets pending (the Release run's Changesets: summary, or unconsumed on a full clone), and name any leak in the curated page, a breaking one under 需手动处理. It says why this is a step and not a check, with the 18.3.0 measurement. The stale "chore: version packages (rc) #4935" in the First, check paragraph becomes "the Version Packages PR".

Why

The CHANGELOG question

docs/releases-maintenance.md says the per-package CHANGELOG.md files are generated and never hand-edited, and that the curated page is where the platform narrative lives. The CHANGELOG half of the erratum is already automatic: the root version script runs release-pending-publish.mjs annotate-shipped before changeset version, so the next cut renders each of these four entries with a lead line **Shipped in 18.3.0**, whose CHANGELOG missed this entry; listed here one release late. (as 18.3.0 did for four of 18.2.0's). So this PR edits no CHANGELOG and no pending changeset.

Every changeset 18.3.0 skipped

Measured with git log --diff-filter=A --format=%H -1 origin/main -- <f> and git merge-base --is-ancestor <sha> 83d7e4ae over all 43 pending .changeset/*.md on main at c618e890. Four are ancestors of the cut. node scripts/release-pending-publish.mjs unconsumed --version-commit 83d7e4ae --version 18.3.0 (full clone) names the same four:

Changeset	Added by	Operator-visible	On the 18.3 page
29904-type-mismatch-fail-closed.md	4c2cd29a (#29923)	yes, breaking: publish refuses what 18.2.0 accepted	Release facts note, sweep table, upgrade checklist step 2; now also under 需手动处理 with the served refusal (this PR)
29903-base-export-without-pair-extension.md	5f474102 (#29930)	yes: a base's own export no longer carries its .custom pair's extension	Release facts note and sweep table (since #29938)
password-reset-revocation-trail.md	7b2bb668 (#29921)	yes: a self-service reset keeps and stamps sys_session rows (revoke_reason: password_reset) instead of deleting them	Release facts note (since #29938)
org-admin-removal-caller-read.md	72d7db03 (#29932)	yes: an org admin's refused removal answers the same 403 for an unreadable row as for a missing one	Release facts note (since #29938)

The three non-breaking ones need no further line: each is a fix that declares no breaking change and no protocol kind, which the page's 其他修复 section counts but does not list, and the Release facts note already names each with its commit. None of them is in the 其他修复 counts, which come from the CHANGELOGs.

Why #26517 merged stale

83d7e4ae is the squash of #26517 onto 72d7db03. The PR's head b1c4119e (committed 13:39Z) has parent 40a35ded (#29922, 13:07Z). git log --first-parent 40a35ded..72d7db03 is five landings: 7b2bb668 (#29921), 4c2cd29a (#29923), 242665f1 (#29931, a checklist edit), 5f474102 (#29930), 72d7db03 (#29932). git diff --name-only --diff-filter=A 40a35ded 72d7db03 -- .changeset/ lists exactly the four changesets above. The PR was merged at 14:44Z without another refresh. The runbook already said to check the PR is current, but gave no command; the Release run's unconsumed report did warn "Name them in the 18.3.0 release notes", and #29938 named them, but only in the facts note.

Guard or runbook step

Runbook step. scripts/release-pending-publish.mjs (under annotate-shipped, #23818) records why refusing a stale Version Packages PR is not the remedy: main took a changeset-bearing landing about every twenty minutes (77 of 111 landings in 24 h), so such a check would refuse nearly every cut. The repo answers the leak with unconsumed (report) and annotate-shipped (next CHANGELOG). The order allows a guard only if it would not block the release flow on false positives; this one would block on true positives almost every time, so this PR adds no check and no .github/workflows/** edit.

Verification

Gates from node scripts/pm/dispatch-gates.mjs --commands for this change set, run at d7feeed3 after a turbo run build of @objectstack/formula, @objectstack/lint and @objectstack/spec: 51 derived, 51 run, all exit 0; dispatch-gates --ran: "51 derived, 51 run, 0 NOT-MEASURED, 0 UNRUN", exit 0. One family, check:skill-examples, exited 3 on the first pass (packages/client-react/dist not built, nothing measured); after turbo run build --filter=@objectstack/client-react... it exited 0 (283 examples). Among them: check:doc-anchors, check:doc-authoring, check:release-section-coverage (plain, --strict, --self-test), check:closed-ceremony-text, check:issue-citations, check-adr-links.

The step-1 command, replayed on 18.3.0 (origin/main → 72d7db03, origin/changeset-release/main → b1c4119e): merge base 40a35ded, four files listed. Anti-no-op: the same diff from 72d7db03 to itself lists zero.

content/docs/releases/ is release-owned (AGENTS.md); this is the dedicated docs-only PR AGENTS.md prescribes for a factual gap on a releases page, with no code riding along. Changeset: none (skip-changeset), docs only.

Human Minimum

• 1. Schemas start as Zod; packages/spec holds no runtime logic. (not touched)
• 2. Every name I added uses the casing for its kind. (none added)
• 3. No formatter ran. No code changed, so pnpm lint has nothing new to judge.
• 4. One issue, one branch off an up-to-date main, one pull request.
• 5. A change that publishes carries a changeset, and both declaration lines are filled in here and in the changeset. (publishes nothing)
• 6. packages/spec touched: its generated artifacts are regenerated and committed. (not touched)
• 7. No hand edits to content/docs/references/, packages/*/CHANGELOG.md or content/docs/releases/. Edits content/docs/releases/v18/18-3.mdx as a docs-only erratum PR, per AGENTS.md's "factual error on a releases page → dedicated docs-only PR".
• 8. Title, body and comments are in English. (the 维护者速读 block is the dispatch convention)
• The Before Submitting list in CONTRIBUTING.md is done.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WGufziWtqgnT2f4C6ThaSM

[objectstack-fleet]

domain:devx#1 · os-support-ai · session_01WGufzgBDcBNVmSmo7VFHpj

Stamp: 2026-11-04T10:12Z
Head-sha: d7feeed

维护者速读

• 改了什么: 18.3 发布页「需手动处理」补上 fix(lint)!: publish refuses a text-vs-number comparison in a validation rule (or another fail-closed predicate) instead of warning, then refusing every write #29923 的收窄（失败即拒的谓词里文本/布尔字段与数字比大小，18.3.0 在发布时拒收，返回 type-mismatch + params.outcome: 'fail-closed'；main 上 fix(lint)!: a type mismatch in a record-triggered flow condition or an advisory validation rule is served a verdict that says what really happens #29953 已改名为 type-mismatch-fail-closed）。docs/releases-maintenance.md 加了三步编号的发版顺序。
• 为什么改: Version Packages PR chore: version packages #26517 合并时落后 main 5 次合入，4 个 changeset 的代码进了 18.3.0，CHANGELOG 里却没有。其中破坏性的那条，升级的人此前在发布页找不到实际的拒绝码。
• 风险与回滚: 只改两份文档，不动代码、changeset、生成的 CHANGELOG 或 workflow。回滚就是 revert。
• 先看: 18-3.mdx 第 284 行起新增的那条，以及 releases-maintenance.md 的「The cut, in order」。
• 两分钟验证: 在完整 clone 上跑 node scripts/release-pending-publish.mjs unconsumed --version-commit 83d7e4ae --version 18.3.0，应列出 4 个 changeset。
• 需要你做的: 无。维护者已于 10:11Z 批准落地，席位挂 auto-merge。
• 席位意见: ACCEPT。选运行手册步骤而不加守卫是对的：release-pending-publish.mjs 里 release(next): 18.0.0-next.2 shipped 11 changesets with no CHANGELOG entry (the version PR merged behind main; #21361's class, in pre mode) #23818 的测量（每 20 分钟一次带 changeset 的合入）说明守卫会拦住几乎每次发版。

席位核对

• 形态: 两份文档，+62/−6，非受管面（check-governed-merges.mjs --pr 30041: 0 of 2 paths governed; 68 lines ≤ 3000）。check-owed-reviews.mjs 不列本 PR，无欠复核。
• 前提实测: fix(lint)!: a type mismatch in a record-triggered flow condition or an advisory validation rule is served a verdict that says what really happens #29953 已合并（9037b13d, 2026-11-03T23:27Z），所以「main 上已改名」成立。release-pending-publish.mjs 有 unconsumed 子命令和 Changesets: 摘要行（L14、L508），release.yml L1142 有 NOT MEASURED 分支。锚点 #metadata-the-build-lint-and-save-doors-now-refuse 解析到第一个同名标题（L284，正是新增条目所在），#release-facts-as-measured 在 L86。npm latest = 18.3.0。
• 门禁 check-runs（钉 d7feeed3，席位读数）: 17 success，19 skipped，10 in_progress（Test Core 1-3/8、Build Docs、Lint · docs & code guards、Lint · repo & tooling gates、Lint · CI, release & engine gates、Lint · ESLint、Type Check · consumer gates、Type Check · source gates）。未结论的由 auto-merge 等全绿。dev 本地 51/51 exit 0。
• 接受的偏差: 新增条目末尾缺句号（"…fix(lint)!: publish refuses a text-vs-number comparison in a validation rule (or another fail-closed predicate) instead of warning, then refusing every write #29923)"），不值一轮。attribution 指向卡线程而非席位线程。relay 首次 pr_create 遇 GitHub 502，未创建，重试成功。
• 范围外去向: 无。三个非破坏性漏条（fix(objectql, metadata-protocol): a base package's own export carries its objects without its .custom pair's extension #29930、fix(plugin-auth): a session a password reset ends leaves a revocation trail #29921、fix(plugin-security): an organization administrator's refused assignment write answers the same for a row it cannot read as for a missing one #29932）已在 Release facts 点名，不另加行。CHANGELOG 下次发版由 annotate-shipped 补写。Skills-docs: none。
• 落地条款: 维护者批准（项目内 10:11Z「以上我都批准了，通知车道落地」）。席位 pr_ready + automerge_enable，合并后关卡 release 18.3.0: #29923's fail-closed type-mismatch refusal shipped in the 18.3.0 packages with no CHANGELOG line (its changeset was not consumed) #29957。