Technical enablement

Release notes

What's new in {{product.name}} and this enablement portal. Newest first. Entries are written so anyone on the team can follow them: what changed, and what it means for the people using or selling {{product.name}}. Breaking changes and migration notes are called out explicitly.

ⓘ

Posting a new release. Add a new <h2> block at the top of the list below, following the template in the page source (date badge + Added / Changed / Fixed groups). Keep entries short and in plain language: lead with what someone can now do, not with the component that changed. The newest entry should always be first, and should also be summarised in the "Latest updates" teaser on the overview. Delete the example entry below once you have posted a real one.

[Example] Version 1.0 baseline Example 2026-01-15

[Example entry, replace or delete.] A one-paragraph summary of the release: the theme, and why it matters to the people using or selling {{product.name}}.

Added

  • [Replace: a new capability.] Describe what a user can now do and where to find it.

Changed

  • [Replace: a behaviour change or improvement, and who is affected.]

Fixed

  • [Replace: a defect that was resolved, described by its symptom rather than its cause.]