Skip to content

🔖 chore(release): core@3.8.0 + cli@3.6.3 + template@3.7.0 - #58

Merged
Lands-1203 merged 1 commit into
mainfrom
chore/release-core-3.8.0
Sep 3, 2026
Merged

🔖 chore(release): core@3.8.0 + cli@3.6.3 + template@3.7.0#58
Lands-1203 merged 1 commit into
mainfrom
chore/release-core-3.8.0

Conversation

@Lands-1203

Copy link
Copy Markdown
Collaborator

发版摘要

组件 旧版本 新版本 bump 原因
Core 3.7.2 3.8.0 minor PR #55routing.match() 完整消费 matcher 4 字段;PR #57 补齐 Agent 侧规则 + Core templates 新建 topic
CLI 3.6.2 3.6.3 patch 按 CLI-pin-Core 联动制(PR #53)同步升级 packages/cli/package.json 里的 @double-coding/flow2spec-core 精确 pin
Template 3.6.2 3.7.0 minor 新写作准则 + 新 topic + 双语 index/unified-entry 同步——下游拿到新模板可直接用 4 字段能力
Protocol 2 2 不变 公共协议未破坏

发布计划

合并本 PR 后:

  1. 打 tag core-v3.8.0npm publish @double-coding/flow2spec-core
  2. 打 tag cli-v3.6.3npm publish @double-coding/flow2spec
  3. 先 Core 后 CLI(按 repo-dev-workflow-constraints 硬约束)

门禁

  • npm test:15 个脚本全绿(含 routing semantics tests passed)
  • npm run pack:check:Core 280.6kB / 126 files、CLI 15.3kB / 3 files
  • node scripts/test-package-install.js:ok
  • flow2spec kb check --strict:knowledge check: ok / topics: 20 / routing drift: no
  • npm run version:check:versions are consistent

相关

后续动作(不阻塞本 PR)

.claude/rules/repo-dev-workflow-constraints.md 里"CLI 对 Core 使用 caret range ^3.5.0"是 PR #53 之前的旧口径,与当前 CLI-pin-Core 联动制不符;发版后可以起一个小 PR 修正该规则,与 PR #53 引入的实际行为对齐。

- Core 3.7.2 → 3.8.0(minor):PR #55 让 routing.match() 完整消费
  matcher 4 字段(includeAll/excludeAny/excludeAll);PR #57 补齐
  Agent 侧规则 + Core templates 新建 kb-routing-summary topic。
- CLI 3.6.2 → 3.6.3(patch):按 CLI-pin-Core 联动制同步升级依赖固定版本
  (packages/cli/package.json 里 flow2spec-core 精确 pin 到 3.8.0)。
- Template 3.6.2 → 3.7.0(minor):新增 f2s-topic-authoring §3「matcher
  分片字段语义」写作准则、Core templates 双语新建 kb-routing-summary
  topic、双语 index / unified-entry 同步 4 字段口径——下游拿到新模板
  后能直接使用 4 字段能力。
- Protocol 2 不变(公共协议未破坏)。
- 门禁全绿:npm test / npm run pack:check / test-package-install / kb check --strict。
@Lands-1203
Lands-1203 merged commit c1b3ec9 into main Sep 3, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant