[os-steve]

Requested by Steve · project thread

Release blocker for 18.2.0. No card: the maintainer asked for it directly in the project thread ("阻塞项你现在优先解决", 2026-10-27 04:16Z).

维护者速读

• 改了什么：.changeset/26095-publishing-metadata.md 第 74 行 'create-objectstack': patch--- 拆成 patch 和 --- 两行。没有改任何包名、bump 级别或正文。
• 为什么改：frontmatter 一直没有闭合，@changesets/parse 抛出 "missing or invalid frontmatter"，changeset version 直接失败。从 10-26 18:14Z 起，定时的 Version PR maintenance 两次都红在这里，所以 chore: version packages #25640 一直停在 d1ea2363。
• 风险与回滚：只改一个换行。回滚就是 revert，changeset version 会重新失败。
• Check Changeset 会保持红色，这是预期的。 这个 PR 改了一个不是它自己加的 changeset，属于 finding: random changeset filenames collide silently across parallel agents — a round overwrote a sibling PR's minor changeset and every gate stayed green #17712 说的 DELIBERATE CORRECTION 类，处理方式见下文。

What changes

.changeset/26095-publishing-metadata.md (added by #26198): on line 74 the closing --- of the frontmatter was glued to the last release line. This PR splits that line so the frontmatter closes. The diff is one line in, two lines out.

Why

changeset version reads every pending changeset. This file threw, so the whole command exited 1. Run 40426048088 (00:23Z) shows it in its Version PR maintenance job:

could not parse changeset - missing or invalid frontmatter.
  at parseChangesetFile (@changesets/parse@1.0.0 ...)

Run 40375928411 (10-26 18:14Z) is the earlier red. The 13:36Z run, before #26198, was green.

Pending release note correction (#17712, DELIBERATE CORRECTION)

This PR changes .changeset/26095-publishing-metadata.md, a pending release note it did not add. The correction leaves the note's meaning alone: the same 73 patch lines and the same body, with only the missing line break restored. Restoring the base text would put the parse failure back. Per the pr-automation.yml route 0 text, no skip-changeset label is applied, and Check Changeset is left red. That check is not a required context. Confirmation: the maintainer's request quoted above.

Verification

• Ran @changesets/parse 1.0.0 (the version CI resolves) over every .changeset/*.md. Before this PR, 1 of 225 failed, and it was this file. After this PR, 0 of 225 fail.
• changeset version (@changesets/cli 3.0.3) on a scratch worktree of this head: result is in the comment below.

Clause-②: no
Metadata-protocol: none

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; pnpm lint passes.
• 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. (this PR publishes nothing of its own; it repairs an existing changeset)
• 6. packages/spec touched: n/a.
• 7. No hand edits to content/docs/references/, packages/*/CHANGELOG.md or content/docs/releases/.
• 8. Title, body and comments are in English.
• The Before Submitting list in CONTRIBUTING.md is done.

---

Generated by Claude Code

[os-steve]

changeset version verification for this PR: I ran @changesets/cli 3.0.3 in a scratch worktree of main @ bb60b86f with this PR's one-file change applied. The repo's .changeset/config.json and changelog module were used, and nothing was committed.

🦋 changeset v3.0.3
All files have been updated. Review them and commit at your leisure
exit=0

• All 225 pending changesets were consumed (225 D), and 238 files were modified (M).
• The fixed group landed on 18.2.0. Checked on packages/spec/package.json and ui/packages/plugin-ai/package.json.

On main without this change, the same command fails at parse on 26095-publishing-metadata.md. That is the error the scheduled Version PR maintenance job has been hitting.

---

Generated by Claude Code

[os-steve]

Check Changeset is red, and that is expected. The pr-automation.yml route 0 calls this a DELIBERATE CORRECTION: the PR adds no changeset of its own, and its only .changeset row is an M on 26095-publishing-metadata.md. Route 0 says to leave the check red and record the confirmation on the PR. The confirmation is the maintainer's request quoted in the description. The later steps in the job pass: check-changeset-no-major says there is no major bump and finds Clause-②: no / Metadata-protocol: none at patch level.

Check Changeset is not a required context, so auto-merge can still go through on the required checks. I'm not changing anything, and I'm not re-running the check, because a re-run would turn red the same way by design.

---

Generated by Claude Code