v0.60.0

Jazor 0.60.0

其他变更

• 公共 API 兼容性门禁现在覆盖宿主、开发 reload、Jazor.Admin、Jazor.Vue 与已发布 ECMAScript 绑定程序集；缺失候选基线会阻断 CI，候选快照保存在 docs/03-guides/public-api-baseline.snapshot.md。by @devhxj
• Quality Gates 新增隔离输出的 Release 主线测试，并要求手动发布流程同样通过 Pinia 生态验证；Emit 当前套件为 201/201。by @devhxj
• 当前 TDesign 和持续浏览器门禁统一使用 Google Chrome；历史版本记录保持不变。by @devhxj
• 修正 TDesign 1.20.7 声明快照计数漂移，重新生成后保持 120/120 文档组件绑定与 118 个 runtime 组件门禁一致。by @devhxj
• Quality Gates 新增独立 Vue binding contract job，发布候选会强制检查三套生成快照、manifest 与上游版本一致性。by @devhxj
• Vue binding contract job 现在上传完整检查日志，失败运行也保留可追溯证据。by @devhxj
• 重新采集并统一 Compiler 与 Razor SG 覆盖率证据，当前分别为 10711/10711、99.42%/97.15% 与 4982/4982、97.53%/94.30%（行/分支）。by @devhxj
• Quality Gates 每周归档 RazorVue clean/incremental 构建趋势；benchmark 同时生成 JSON 与 Markdown 摘要，持续观测不等同于宣称优化收益。by @devhxj
• Wiki Chrome browser 与发布 consumer 现以 Node 20/22 矩阵持续验证；发布打包流程仍使用 Node 22。by @devhxj
• inspect-razorvue-chain.cs 新增 SARIF 2.1.0 输出，断链诊断可由 IDE 直接消费稳定 ID、HelpLink 和作者源位置。by @devhxj
• 发布 workflow 在 NuGet 打包前强制校验带日期的 CHANGELOG 版本章节，避免无整理的自动生成说明进入正式发布。by @devhxj
• 新增 verify-release-candidate.cs 与手动 Release Candidate workflow，统一归档 1.0 候选的 API、质量、包形状和 SPA/SSR consumer 证据。by @devhxj
• 发布候选覆盖率报告现在写入候选专用目录，并连同工具链矩阵一起归档，避免 RC 证据散落在共享质量目录。by @devhxj
• Wiki 文档导入器现在默认排除大型机器快照（*.snapshot.md），并提供显式开关用于完整检查，避免发布 consumer 因 C# 用户字符串池上限失败。by @devhxj

Other Changes

• Extend the public API compatibility gate to host, development reload, Jazor.Admin, Jazor.Vue, and published ECMAScript binding assemblies. CI now blocks when the candidate baseline is missing; the retained snapshot is docs/03-guides/public-api-baseline.snapshot.md. by @devhxj
• Add an isolated-output Release main test lane to Quality Gates and require Pinia ecosystem verification for manual publishing as well as tag publishing; the current Emit suite is 201/201. by @devhxj
• Current TDesign and continuous browser gates consistently use Google Chrome; historical release entries are unchanged. by @devhxj
• Correct the TDesign 1.20.7 declaration snapshot count drift so the regenerated metadata remains aligned with the 120/120 documented bindings and 118 runtime component gate. by @devhxj
• Add a dedicated Vue binding contract job to Quality Gates so release candidates enforce generated snapshot, manifest, and upstream version consistency across all three binding libraries. by @devhxj
• Upload the complete Vue binding contract log, including failed runs, as traceable CI evidence. by @devhxj
• Recollect and align Compiler and Razor SG coverage evidence: 10711/10711 with 99.42%/97.15%, and 4982/4982 with 97.53%/94.30% (line/branch). by @devhxj
• Archive weekly RazorVue clean/incremental build trends in Quality Gates; the benchmark now emits JSON and Markdown summaries, preserving observation without claiming an optimization gain. by @devhxj
• Run Wiki Chrome browser and publish consumer checks across a Node 20/22 matrix; the packaging workflow remains on Node 22. by @devhxj
• Add SARIF 2.1.0 output to inspect-razorvue-chain.cs, allowing IDEs to consume stable IDs, HelpLinks, and authored source locations for broken-chain diagnostics. by @devhxj
• Require a dated, non-empty CHANGELOG version section before NuGet packaging so uncurated generated notes cannot enter an official release. by @devhxj
• Add verify-release-candidate.cs and a manual Release Candidate workflow to archive API, quality, package-shape, and SPA/SSR consumer evidence in one 1.0 candidate run. by @devhxj
• Write release-candidate coverage reports under the candidate directory and archive them with the toolchain matrix so RC evidence is not scattered across the shared quality directory. by @devhxj
• Keep large machine snapshots (*.snapshot.md) out of the default Wiki browser catalog, with an explicit full-import switch for evidence checks, so release consumers do not hit the C# user-string pool limit. by @devhxj

Full Changelog

v0.50.0...v0.60.0