zyycnandClaude 55e87c3b16 docs: phrase the clean-break warning per major, not 2.x/3.x ...

The release body ships on every future release, so a hardcoded "from
2.x" would be stale by 4.0. State the invariant instead: schema and
configuration are compatible within a major only, and self-update refuses
cross-major targets from 3.0 on.

Co-authored-by: Claude <noreply@anthropic.com>

2026-07-26 23:43:14 +08:00

..

_container.yml

chore(release): prepare v3.0.0

2026-07-25 01:54:18 +08:00

_quality.yml

ci: freeze applied migrations behind a sha256 manifest

2026-07-26 23:20:38 +08:00

ci.yml

ci: speed up validation pipelines

2026-07-16 16:07:55 +08:00

release.yml

docs: phrase the clean-break warning per major, not 2.x/3.x

2026-07-26 23:43:14 +08:00

security-scan.yml

chore(deps): bump setup-node to 7.0.0

2026-07-16 01:51:31 +08:00