Cumulative Flow follows your workflow mapping
Throughput and the completion ticks now count an item when it first reaches a state you mapped as Done, the same rule as every other view. A state Azure DevOps treats as closed but your mapping does not, such as Ready to Release mapped as review, is no longer counted as completed, so Throughput matches the Done band.
Sub-teams says what it counts
The Blocked column is now "Blocked or stalled", because it lists the same items as the Blocked Items tab in Aging & Blocked: items marked blocked, or not moved for 5 days or more. Carryover shows a dash with a note when Azure DevOps has no next sprint yet, and "Older than usual" says when your items usually finish within a day.
Aging & Blocked for fast teams
For a team whose items usually finish within a day, items are labelled by the fixed bands (over 3 days, over 6 days) instead of "over p85", and the thresholds line says so.
What you need to do
Nothing. Azure DevOps updates the extension automatically. Cumulative Flow Throughput can be lower for teams that map a closed state, such as Ready to Release, as not done: it now matches the Done band.