XingfenD
cc2156b44d
The pins still named the feat/submission-preview work branch, so fresh clones landed on WIP instead of the integration branch.
34 lines
2.7 KiB
Markdown
34 lines
2.7 KiB
Markdown
# Changelog / 更新日志
|
||
|
||
All notable changes to this repository should be documented in this file.
|
||
本仓库的重要变更建议统一记录在此文件中。
|
||
|
||
The format loosely follows Keep a Changelog and can be adapted to the team's habits.
|
||
本文档参考了 Keep a Changelog 的思路，也可以根据团队习惯调整。
|
||
|
||
## [0.2.1] - 2026-09-29
|
||
|
||
### Fixed / 修复
|
||
|
||
- `clone_all.sh` pins `master` for `crearte` and `crearte-server` instead of the stale `feat/submission-preview` work branch — fresh clones and updates land on the integration branch that carries the merged roadmap work. (Note: `update_repo` switches clean checkouts to the pinned branch; dirty ones are skipped.)
|
||
- `clone_all.sh` 中 `crearte` 与 `crearte-server` 的引导分支由过时的 `feat/submission-preview` 工作分支改为 `master` —— 全新克隆与更新落在承载路线图已合并工作的集成分支上。（注意：`update_repo` 会把干净的 checkout 切到钉子分支，脏工作树自动跳过切换。）
|
||
|
||
## [0.2.0] - 2026-09-29
|
||
|
||
### Changed / 变更
|
||
|
||
- Roadmap delivered: P0 (known-defect cleanup — CORS `If-None-Match` fix in crearte-server `a8ea755`, compose key-store drift cleanup in crearte-deploy `27044be`) and P4 (author page `/users/:user`, crearte `f12cbf1`) are merged to their repos' master and pushed; roadmap statuses updated.
|
||
- 路线图交付：P0（已知缺陷清理——crearte-server `a8ea755` 的 CORS `If-None-Match` 修复、crearte-deploy `27044be` 的 compose 密钥库遗留清理）与 P4（作者主页 `/users/:user`，crearte `f12cbf1`）均已合并至各仓 master 并推送；路线图状态已更新。
|
||
|
||
## [0.1.0] - 2026-09-29
|
||
|
||
### Added / 新增
|
||
|
||
- Added `docs/ROADMAP.md`: the cross-repo roadmap decomposed into sub-projects P0–P8 (ops foundation → product value → governance), with ordering rationale and a doc index for future specs and plans.
|
||
- 新增 `docs/ROADMAP.md`：跨仓库路线图，分解为 P0–P8 子项目（上线底座 → 产品价值 → 治理长尾），含排序理由与后续 spec/计划的文档索引。
|
||
|
||
### Changed / 变更
|
||
|
||
- Doc convention: all specs, implementation plans and cross-repo coordination docs now live in the monorepo `docs/` instead of per-repo `docs/superpowers/`; this supersedes the crearte-deploy 0.3.0 "canonical home" convention. Commits in the monorepo wrapper may go directly to `master` (user-approved); the three inner repos keep their own branch rules.
|
||
- 文档约定：所有 spec、实现计划与跨仓库协作文档统一收归 monorepo `docs/`，不再散落各内层仓库的 `docs/superpowers/`；此约定取代 crearte-deploy 0.3.0 的「canonical home」约定。monorepo wrapper 可直接提交 `master`（维护者确认），内层三仓仍遵循各自分支规范。
|