docs(releases): v17 升级指南收录两条 console 破坏性迁移,console 段 pin 区间推到 f995a452d2ca (#6106) - #6109
Merged
Merged
Conversation
…a452d2ca (#6106) 「Breaking changes & migration」章节此前完全不含 PR #6097 带进来的两条作者侧 破坏性迁移(widget 元数据单载体 objectui#3233、flow 节点几何 objectui#3172), 它们只活在 .changeset/ 这一发布记录的输入层;rc.4 一发,正在升级的作者在文档站 上读不到。本次按该页既有条目格式补两条 ### 条目(what broke / who is affected / 机械迁移 diff / 源链接),并把 console 段标题的 pin 区间行由 `4a4829d0ef39 → 785b8a5d432c` 更新为 `→ f995a452d2ca`。 同页 rc.1 窗口开头「The Console pin is **unchanged** at 785b8a5d432c」是同一个 陈旧事实的另一处落点 —— 若只改标题行,该页会在一屏之内自相矛盾,故一并按事实 更正(独立 hunk,可单独回退)。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BDmDsu2575gDxeMCxXhDE3
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
hotlong
marked this pull request as ready for review
August 7, 2026 02:22
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #6106
rc.4 发布前置的 PR A(docs-only)。只改
content/docs/releases/v17.mdx一个文件,不含任何代码/脚本改动,因此没有 changeset(走skip-changeset)。这是 CLAUDE.md「不要在代码 PR 里改content/docs/releases/」条款所指的那条正当路径:专门的 docs-only PR 修正该页的事实错误。为什么现在改
PR #6097 把 console pin 推到 objectui
f995a452d2ca,随之 vendored 进来两条 作者侧破坏性迁移。它们此前只活在.changeset/(发布记录的输入层),整个content/docs/下对withFieldCarrier/FieldWidgetComponentProps/FlowNode.position/node.ui零命中 —— rc.4 一发,正在升级的作者在文档站上读不到,这是新用户第一眼撞上的坑。改了什么(三处 hunk)
1. 「Breaking changes & migration」新增两条
###条目插在
### Dead spec clusters removed与### Smaller breaking changes之间(不动任何既有条目顺序)。格式对齐同章节里唯一的 objectui 来源前例### An action param's picker target is 'reference', and only 'reference' (objectui#3203):声明句式标题 + 源链接括注、diff迁移块、加粗小结句。### Field widgets receive their metadata on one key, 'field' (objectui#3233)——FieldWidgetComponentProps不再声明schema;两个生产者收敛,约 30 处field || schema消失。给出两段机械迁移:读法去掉 fallback;能被SchemaRenderer派发的 widget 用withFieldCarrier包一次注册。点名受影响者(第三方 widget 继续读props.schema会拿到undefined并静默渲染空态),并保留源 changeset 的两条「没变的东西」——宿主元数据(SDUI JSON)不变、schema仍是非 field-widget 组件的通用 SDUI prop。### Flow node geometry is the spec's 'FlowNode.position' (objectui#3172)—— 三处写入点统一写position: { x, y },画布在首个 patch 上把遗留ui抬到position并删键。保留源 changeset 的关键定性:这是行为修复而非改名(FlowNodeSchema自 未知键静默剥离仍是全仓默认:把 #3405 的 strict 收紧从一个 schema 推广到整个可授权面(ADR-0078 完整性闸门) #4001 起.strict(),ui是unrecognized_keys,服务端 422 —— 拖一下节点就存不了流程);读取侧向后兼容(manualPosition()优先position、回落遗留ui),但那是迁移路径不是第二契约。两条正文均取自 objectui@
f995a452d2ca的源 changeset(field-widget-single-metadata-carrier.md/flow-node-geometry-is-spec-position.md)与 objectui#3233 / objectui#3172。2. console 段 pin 区间行(原第 1969 行)
并在该段说明后补四行(既有的 143 commits / five pin moves 叙述原样保留,不重写):
数字是实测的,不是估的:
git rev-list --count --no-merges 785b8a5d432c..f995a452d2ca= 129,与两份 pin changeset 自报的 31 + 98 non-merge commits 吻合;git merge-base --is-ancestor确认该区间内的 pin 落点只有f5bc4c78be76与f995a452d2ca两次(其余 console changeset 的 sha 都不在785b8a5d432c之后)。3. rc.1 窗口开头的同一陈旧事实(独立 hunk,可单独回退)
Issue 只点名了第 2 处,但那句话与它是同一个事实的另一处落点;只改标题行会让该页在一屏之内自相矛盾(上面说推进到
f995a452d2ca,下面说 pin unchanged 在785b8a5d432c)。故按事实更正,行数不变(5 行换 5 行):若维护者认为这一处应留给 rc.4 的发布记录统一处理,这是独立的第三个 hunk,单独 revert 不影响前两处。
验证
纯文本改动,没有反向验证可做(不存在会因这次改动翻转的断言);跑的是 CI 对
content/docs/**实际会跑的门禁,全绿:pnpm check:release-notesOK — every released major has a curated, navigable release page.pnpm check:doc-authoring363 files clean — no bare metadata literals.pnpm check:docs-audit-scope178 hand-written doc(s)同步 +9 page(s) under content/docs/releases/ review-onlypnpm check:adr-anchorsOK (34 anchored file(s), every governing ADR still referenced).pnpm check:nul-bytesOK (scanned 5857 tracked text file(s) … no raw ASCII control bytes).pnpm check:prerelease-pinsNo stable release yet for 11 prerelease pin(s)apps/docs的fumadocs-mdx重新生成通过;另用@mdx-js/mdx@3.1.1直接compile(v17.mdx, { format: 'mdx' })→ MDX COMPILE OK改动面:
1 file changed, 90 insertions(+), 6 deletions(-),只有content/docs/releases/v17.mdx。关联
.changeset/console-f995a452d2ca.md的 flow 条目补**BREAKING (v17)**标注(同一 issue 的第 3 项,单独 PR)。major声明级别,而 objectui 在 v17 窗口内把破坏性声明为minor+ 正文标注 #6099 —— digest 只读首段导致该标注丢失的机制盲区,不在本 PR 范围。Generated by Claude Code