Skip to main content
Each release note in the Changelog follows a consistent structure. This page describes what each section means.

Sections

Release header

The release version, date, and components affected.

Highlights

The 2–4 most user-visible changes in the release. Scan this first.

New features

User-facing capability additions. Each entry links to the relevant doc page.

Improvements

Performance, reliability, or usability improvements that don’t add new surface area.

Bug fixes

Fixed issues. Each entry references the bug ID (for example, E6-1234) for support reference.

Breaking changes

Anything that changes existing behavior in a way that could affect customer queries, configurations, or integrations. Always read this section before upgrading.

Deprecations

Features marked for removal in a future version. Lists the deprecated feature, the recommended replacement, and the planned removal date.

Security advisories

Security-relevant fixes. Includes severity (Low / Medium / High / Critical) and whether action is required from customers.

How to use release notes

Versioning

e6data uses semantic versioning: Major version bumps are rare (typically annually). Most releases are minor or patch.

See also

Last modified on September 29, 2026