Product updates

Changes documented.
With useful context.

No public release entries have been approved for this index yet. Future notes will identify the product, release date, affected users, change, action required, documentation, and support path.

Release-note structure

Every update should answer the practical questions.

01

What changed?

Describe the verified product change in plain language.

02

Who is affected?

Name the relevant roles, plans, configurations, or workflows.

03

What action is needed?

State prerequisites, migration steps, deprecation dates, or no-action status.

04

Where is the evidence?

Link versioned documentation, support, status, and trust information when relevant.