One carryover rule in every view
Every view now counts it the same way. An item is carryover when it was in the sprint for at least a day and was not done when the sprint ended, including items moved straight to the next sprint. Items moved back to the backlog count as removed scope, and an item pulled in by mistake and taken out the same day never counts. The percentage is a share of every item in the sprint, so it no longer needs a commitment. Sprint Summary, Sub-teams, Sprint Velocity, the Dashboard, Delivery Signals and Exec Report all use it, with "How carryover is counted" one click away. Your carryover figures may change, mostly because unfinished work moved early to the next sprint now counts.
Related: How carryover is counted
Finished sprints only
A running sprint shows a dash with "Carryover is counted when the sprint ends." Sprint Velocity and Delivery Signals read each finished sprint’s history after the page appears, so carryover fills in a moment later.
Clearer words
The Sprint Summary card says how much committed work was "not delivered", and the Sub-teams "Kept" column is now "Reliability", the word every other view uses.
Every team at a glance
With two or more teams, a "Teams at a glance" table above the cards shows one line per team (delivered of committed, done of all items, scope change and carryover), each matching its card.
Investment Allocation
The Break down by list hides people, link, server and build fields (a field you already chose stays), teams that finished nothing fold into one line, and the subtitle names the field you grouped by.
What you need to do
Nothing. Azure DevOps updates the extension automatically. Expect your carryover figures to change once: they now follow one rule, so the same sprint shows the same number in every view.