Product changes, with dates

What this page includes

The changelog includes customer-facing changes to Eza Cloud.

That includes new features, material fixes, supported stack changes, pricing changes, Beta changes, API changes and deprecations.

The changelog does not include internal refactoring, routine infrastructure work or changes that do not affect customer use.

Release labels

New

Customers can use a new feature.

Improved

An existing feature behaves better without changing its main workflow.

Fixed

A defect is corrected.

Changed

Customers need to adjust a workflow, configuration or expectation.

Beta

The feature is included and supported but excluded from uptime credits.

Breaking change

Customers must update code, settings or deployment workflow.

How Eza announces removals

1. 01Give at least 30 days’ notice for a breaking API or CLI change.
2. 02State the exact removal date in EAT.
3. 03Publish a migration guide before the removal date.
4. 04Email affected organisation Owners when Eza can identify them.
5. 05Keep the old behaviour available during the notice period where technically possible.
6. 06Do not label a breaking change “Improved.”