Split client and server revision tracking
This commit is contained in:
@@ -38,7 +38,8 @@
|
||||
- Runtime/protocol behavior changes: update `docs/runtime-flow.md` and/or `docs/protocol-notes.md`.
|
||||
|
||||
## Versioning & Configuration
|
||||
- Bump `client/public/version.js` on every user-visible change using release version + revision metadata (`CHGRID_RELEASE_VERSION`, `CHGRID_BUILD_REVISION`, and derived `CHGRID_WEB_VERSION`, for example `0.1.0` + `R340`).
|
||||
- Bump `client/public/version.js` on every user-visible client change using shared release version + client revision metadata (`CHGRID_RELEASE_VERSION` and `CHGRID_CLIENT_REVISION`, for example `0.1.1` + `R350`).
|
||||
- Keep the server-only revision in `server/app/version.py`; server revisions do not require a client version bump unless browser code/assets changed.
|
||||
- Commit each completed logical change; include the version bump in that same commit when client behavior changes.
|
||||
- Docs-only changes do not require a version bump unless explicitly requested.
|
||||
- Do not duplicate version constants elsewhere in client code.
|
||||
|
||||
Reference in New Issue
Block a user