docs(hemx): define v1 versioning policy

Add a compact semver and upgrade policy for v1: stable beginner APIs, stable wire/runtime compatibility, advanced escape-hatch tier, breaking-change rules, upgrade-note template, and release checklist. req: abi/001 req: abi/002 req: abi/003 req: abi/004 req: abi/005 req: public_api/001 req: public_api/002 req: public_api/005 req: runtime/003 req: runtime/004
2026-06-05 09:49:30 +02:00
parent c8c71deb68
commit 1fbeeb52b8
3 changed files with 152 additions and 1 deletions
@@ -104,7 +104,8 @@ For v1, document changes in three buckets:

 Upgrade notes should explain what changed, whether generated code must be
 regenerated, whether `/hemx.js` must be rolled with the server, and what fallback
-users see if an old page talks to a new server.
+users see if an old page talks to a new server. Use `docs/versioning.md` as the
+release-policy checklist.

 ## Deployment checklist