[objectstack-fleet]

Requested by Warren · project thread

Fixes #26631

Clause-②: no
Metadata-protocol: none

维护者速读

• 改了什么: 升级指南 upgrading.mdx 的「每个版本的升级说明在哪」表格加了一行 v18.2.0,指向 18.2.0 发布页的升级清单。
• 为什么改: 18.2.0 已发布且发布页带升级清单,但这张表停在 v18.1.0,从 18.1 往上升的用户在指南里找不到 18.2 的入口。
• 风险与回滚: 纯文档一行,无运行时改动,不发包;回滚 = revert 本 PR。
• 先看: content/docs/upgrading.mdx 「Per-release specifics」表的第一行。
• 两分钟验证: 打开 /docs/upgrading,点表中 v18.2.0 一行的链接,应落到 18.2.0 发布页的「Upgrade checklist」小节。
• 需要你做的: 无,席位落地。

What changes

One row added to the per-release table in content/docs/upgrading.mdx, above the v18.1.0 row:

| v18.2.0 | [Upgrade checklist — 18.2.0](/docs/releases/v18/18-2#upgrade-checklist) |

Why

The table stopped at v18.1.0, while content/docs/releases/v18/18-2.mdx (#26494) ships ## Upgrade checklist (line 910), so the anchor is #upgrade-checklist.

Nothing else moves with it: no other list in upgrading.mdx stops at 18.1, and no test or script pins the table's rows (searched scripts/, packages/, .github/). content/docs/releases/** and references/** are untouched. content/docs/** publishes no package, hence skip-changeset.

Verification

node scripts/pm/dispatch-gates.mjs --commands derived 44 gate families for this diff; all 44 exit 0, and --ran reconciles 44 derived / 44 run / 0 NOT-MEASURED. That includes check:doc-anchors, check:docs-redirects, check:corpus-claim-drift and check:docs-transcript-drift (the last after building @objectstack/lint). Prerequisite builds before the first exit 0: @objectstack/lint..., @objectstack/formula, @objectstack/spec, @objectstack/client(-react)....

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. (no names)
• 3. No formatter ran; pnpm lint passes. (one mdx row, outside ESLint's globs; not run locally)
• 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/.
• 8. Title, body and comments are in English. (except the 维护者速读 channel)
• The Before Submitting list in CONTRIBUTING.md is done.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JQwxbWQbmPGoJDwc2QWoUJ

[objectstack-fleet]

维护者速读

• 改了什么:content/docs/upgrading.mdx 的「Per-release specifics」表在 v18.1.0 上面加一行 v18.2.0,链到 18.2.0 的升级清单。
• 为什么改:18.2.0 已发布,但升级指南的表停在 v18.1.0,运维人员找不到 18.2.0 的升级清单。
• 风险与回滚:只加一行文档,回滚 = revert 本 PR。
• 先看:content/docs/upgrading.mdx 第 466 行附近。
• 两分钟验证:打开 /docs/upgrading#per-release-specifics,点 v18.2.0 那一行,应跳到 18-2 页的「Upgrade checklist」。
• 需要你做的:无,席位落地。
• 席位意见:锚点已对照 releases/v18/18-2.mdx 的 ## Upgrade checklist 标题核过,其他地方没有同样停在 18.1 的列表。

席位核对

ACCEPT · domain:devx#1 · session_01JQwxbaFpnMwgpCgneKe2qS · head eab39f53e0 · 2026-10-27T18:07Z

1. Shape: 1 file, +1/−0: content/docs/upgrading.mdx, one row above v18.1.0 in the shape of the rows beside it. Not governed (check-governed-merges --pr 26830). File surface as in claim 6448957291; Fixes #26631.
2. Read by the seat: the row. Its anchor #upgrade-checklist matches ## Upgrade checklist at content/docs/releases/v18/18-2.mdx L910 on main; releases/** and references/** are untouched.
3. Gates: head check-runs on eab39f53e0: 30 success, 16 skipped, 0 failing; check-expected-skips --pr 26830: OK, all 16 in main's roster; mergeable clean. Thread's local run: dispatch-gates 44/44 exit 0, 0 NOT-MEASURED. Report 6449453411.
4. Accepted deviations: none.
5. Out of scope: none found; the thread checked that no other list in upgrading.mdx stops at 18.1 and no test pins the table. Skills-docs: not owed.
6. Landing: not governed, CI green on this head, mergeable clean ⇒ the seat readies it and arms auto-merge through the relay. At merge docs(upgrading): the Per-release specifics table has no v18.2.0 row — 18.2.0 is published and its upgrade checklist (releases/v18/18-2) is not linked from the upgrade guide #26631 closes and leaves pm:dispatched.

---

Generated by Claude Code