docs(app-shell): the wait-key retirement lands in spec 17.0.0, not the "18" its tombstone claims (#3101) - #3105
Merged
Conversation
…e "18" its tombstone claims (#3101) `zodKeys`' TSDoc named "spec 18" as the bump that arms the `wait` panel, copied from framework#4198's own prose. There is no 18 to wait for: `@objectstack/spec` publishes `latest` 16.1.0 / `rc` 17.0.0-rc.0, and changesets computes a pre-release train off the last *published* major — so the retirement's `major` changeset resolves to 17.0.0-rc.x, not 18. framework main already carries both tombstones (ab1633122) with `PROTOCOL_VERSION = '17.0.0'`. Comment only; the filter and the assertions are unchanged. The correction matters because it names the trigger: the panel fires on the next rc this repo installs, not on a major the current release train cannot produce. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
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.
#3101 记了一条待办:
wait表单还提供waitEventConfig.timeoutMs/.onTimeout,而 framework#4198 已经给它们上了墓碑。待办本身成立 —— 触发时机写错了。没有 18 可等
zodKeys的 TSDoc(以及 #3101 正文、以及 framework#4198 自己的 changeset 正文)都写着这两个键"retired at spec 18",于是 #3101 的处置写成「在把@objectstack/spec升到 18 的那个 PR 里一并处理」。当前的发布机器产不出 18:latest= 16.1.0,rc= 17.0.0-rc.0 —— 17.0.0 从未发布.changeset/pre.jsonmode: "pre",tag: "rc",@objectstack/specinitialVersion = 16.1.0'@objectstack/spec': major17.0.0-rc.1)ab1633122),同一棵树上PROTOCOL_VERSION = '17.0.0',且protocol-version.test.ts把它钉死在 package.json 的 major 上"18" 是从在研版本号
17.0.0-rc.0往上数了一位得来的,而 changesets 是从 16.1.0 往上算的。framework main 上 9 处墓碑文案写 18、32 处写 17;那 9 处的共同点只是"在 rc.0 切出之后才落地",全都还在 17 这趟车上(objectstack#3909 "the 17.0.0 train" 仍开着)。已装的 rc.0 里spec 18出现 0 次,spec 17出现 200 次。这条注释为什么值得改
它是这个 ratchet 的触发条件说明。写成"等 18",这条待办就会等一个不会到来的事件,然后在下一次 rc 刷新时被动踩雷 —— 正是 #3101 想避免的那件事。改后的注释把推导过程也记下来,免得下一个人重新数错一遍。
仅注释;
zodKeys的过滤逻辑与三处断言一字未动。不受影响的部分
不要单独先删这两个字段仍然成立,只是理由要换:sibling-block 断言是双向的(flow-node-config.spec-reconciliation.test.tsL192-199),而已装的 rc.0 里waitEventConfig仍把两个键声明为活键,现在删会在反方向红(declared by the spec block but absent from the designer form)。轴是"已装 rc.0 vs 下一次 rc",不是"17 vs 18"。验证
(5 skipped = script/subflow/decision 三个 feature-detect 面板,已装 spec 尚未导出它们的契约 —— 与改动前一致。)
Related
wait表单仍提供已退役的waitEventConfig.timeoutMs/.onTimeout—— 下一次 spec rc 刷新会被对账测试点名 #3101 —— 待办本体;正文的触发条件已同步更正@objectstack/spec18」,而这些键随 **17.0.0** 发布 —— 处方给了作者一个不会到来的版本号 objectstack#4350 —— framework 侧同源的 10 处墓碑文案(含本 PR 引用的那两处)版本号更正waitEventConfig.timeoutMs/.onTimeout—waitnever had a timeout (#4158) objectstack#4198 —— 退役这两个键的 framework PRscriptoffers three broken options and cannot author the one that works objectstack#4278 / #4325 —— 引入对账的两半🤖 Generated with Claude Code