Cordis 4.0.0-rc.9

[shigma]

Bug Fixes

• core: dispatch symbol and prototype-named events (fix(core): dispatch symbol and prototype-named events #51)
• core: do not re-enter lifecycle from a failed outcome (fix(core): do not re-enter lifecycle from a failed outcome #98)
• timer: settle concurrent interval reads in order (fix(timer): settle concurrent interval reads in order #53)
• types: widen optional properties for exactOptionalPropertyTypes (fix: widen optional properties for exactOptionalPropertyTypes #68)

---

问题修复

• core: 修正以 symbol 或 Object.prototype 同名属性（如 toString）作为事件名时的派发 (fix(core): dispatch symbol and prototype-named events #51)
• core: 已失败的 fiber 不再因 epoch 变化重入生命周期，只能通过 update() 恢复 (fix(core): do not re-enter lifecycle from a failed outcome #98)
• timer: ctx.interval() 迭代器的并发 next() 调用按顺序结算，不再丢弃先前 pending 的 promise (fix(timer): settle concurrent interval reads in order #53)
• types: 放宽可选属性类型以兼容 exactOptionalPropertyTypes (fix: widen optional properties for exactOptionalPropertyTypes #68)

---

Packages

• cordis: 4.0.0-rc.8 → 4.0.0-rc.9
• @cordisjs/plugin-include: 1.0.4 → 1.0.5
• @cordisjs/plugin-loader: 1.0.0-rc.5 → 1.0.0-rc.6
• @cordisjs/plugin-timer: 1.1.2 → 1.1.3

---

This discussion was created from the release Cordis 4.0.0-rc.9.

[Oppenheymu]

stable在向我们招手？

[shigma]

应该还有挺长一段时间

[PerryLink]

Thanks for the release notes format - the per-package bump list is exactly what downstreams need.

From the downstream side: I maintain a family of 38 cordis plugins. They currently validate against the harness's bundled cordis (rc.7-based, plus local patches). We have not yet run the matrix against rc.9, and I would like to offer exactly that: an isolated compatibility run of the full family against rc.9, with per-package results reported back here. If that is useful, is there anything in particular you would like covered (loader mounting, include patches, HMR, timer)?

One registry observation, in case it is unintended: the npm cordis package's latest dist-tag currently points at 4.0.0-rc.9, while the registry so far only carries prerelease 4.0.0-* versions. npm i cordis therefore installs rc.9 today. If latest is meant to stay on a stable line, this may deserve a look before 4.0.0 ships.

感谢这个发布说明格式 - 逐包的版本 bump 清单正是下游需要的。

从下游视角: 我维护着 38 个 cordis 插件家族。它们目前对照 harness 内置的 cordis (rc.7 基 + 本地补丁) 验证。我们还没有对照 rc.9 跑过矩阵, 我正是想提供这件事: 把整个家族在隔离环境里对照 rc.9 跑一遍兼容矩阵, 逐包结果回报到这个讨论。如果有用, 你们特别希望覆盖哪些面 (loader 挂载、include patch、HMR、timer)?

一个 registry 观察, 万一是无意的: npm 上 cordis 包的 latest dist-tag 当前指向 4.0.0-rc.9, 而 registry 迄今只有 4.0.0-* 预发布版本。因此今天执行 npm i cordis 会装到 rc.9。如果 latest 本应留在 stable 线, 在 4.0.0 发布前可能值得看一下。