docs(runtime): align docs with hashed runtime asset
Replace fixed /hemx.js wording with helper-provided runtime asset language so docs match hemx-axum runtime_js_path deployment boundaries. req: axum_integration/005 req: examples/001
This commit is contained in:
+4
-3
@@ -101,7 +101,8 @@ include upgrade notes with this shape:
|
||||
|
||||
### Required actions
|
||||
- Regenerate generated code with `cargo check` or your normal build.
|
||||
- Deploy server and `/hemx.js` from the same release if ABI/fingerprint changed.
|
||||
- Deploy server and the helper-provided runtime asset from the same release if
|
||||
ABI/fingerprint changed.
|
||||
- Update any renamed helpers or advanced calls listed below.
|
||||
|
||||
### Compatibility behavior
|
||||
@@ -135,8 +136,8 @@ Before tagging a v1-compatible release:
|
||||
- Any incompatible generated ABI/runtime change bumps the relevant ABI/fingerprint
|
||||
inputs and has tests for fail-closed behavior. req: abi/005
|
||||
- Advanced APIs touched by the release are still named as escape hatches in docs.
|
||||
- Upgrade notes state whether users must regenerate code, redeploy `/hemx.js`, or
|
||||
change app code.
|
||||
- Upgrade notes state whether users must regenerate code, redeploy the
|
||||
helper-provided runtime asset, or change app code.
|
||||
|
||||
## Policy for v1 cutover
|
||||
|
||||
|
||||
Reference in New Issue
Block a user