Versions and Releases
The version in the documentation header is read from the repository's VERSION file when this site is built. If the build source does not include that file, the header shows a Versions link without a number. Check the version shown by your application to identify the installed version. A documentation version is not evidence of when an environment was deployed.
Reading release notes
- 0.5.88 — Updated User Guides describes the documentation corrections.
- 0.5.87 — Modules and Entitlements describes user-facing changes in that source version.
- Use the current guides on this site for task instructions.
- If an older link brought you here, the former 1.x notes or release template are no longer published as current product history. Their original text remains in the source archive; actual releases have not been renumbered.
Releases and compatibility
A version number alone does not establish that a feature is enabled in your installation. Access depends on effective modules, limits, role, scope and record state. Integration users should also check the relevant Push/Pull contract and any migration note.
There is no fixed weekly or monthly release commitment. A schema change does not by itself mean that every user must perform a manual operation; follow the upgrade instructions for your installation.
After an update
- Check the version shown by the application.
- Open your role's home page and menus.
- If you use integrations, check the measurement flow with an authorized administrator; do not create trial records in production.
- When reporting an issue, include the version, screen, time and error code. Do not send passwords, tokens or API keys.