RELEASE NOTES

Release notes publish customer-relevant change after review.

This index explains how public release information is governed. It does not expose private infrastructure changes, vulnerabilities, or unreviewed internal work.

View documentation

What belongs in a public release note

Customer-visible features, behavior changes, resolved issues, deprecations, migration actions, and documentation updates can be published when product, technical, security, and communication owners approve the wording.

Current publication status

Historical internal commits are not converted into marketing release notes automatically. Reviewed version entries will appear here as they are approved.

How to prepare for change

Use product communication and the applicable customer agreement for release timing. Validate environment-specific changes before production use.

Scope and limitations

  • Absence from this public index does not describe the complete internal change history.

Related Anabhix guidance