release: applying package updates (manual recovery)

[Martin Hochel (Hotell)]

Manual release recovery

The v9 release pipeline run #383600 published all 36 packages to npm successfully**, but then failed when pushing the version bumps back to master:

fatal: Authentication failed for 'https://github.com/microsoft/fluentui.git/'

As a result the packages are live on the registry while the repository still carries the previous versions. npm publishes are irreversible, so this PR moves the repository forward to match the registry.

What this PR does

• Replays the release locally with yarn beachball bump --config scripts/beachball/src/release-vNext.config.js, consuming the change files the failed run never got to commit
• Applies the same precommit fixups a real release runs: dependency-mismatch, normalize-package-dependencies, yarn install --mode=update-lockfile

No versions were hand-edited. Everything is beachball-generated so changelogs and dependency ranges stay consistent.

Verification

A registry sync check confirms every previously desynced package now matches npm exactly:

Checked: 129
  in sync:        128
  npm ahead:      0
  repo ahead:     1   (pre-existing: unreleased work / prerelease dist-tag)

Packages recovered (36)

Package	Before	Now (= npm)
@fluentui/priority-overflow	9.4.2	9.4.3
@fluentui/react-accordion	9.12.2	9.12.3
@fluentui/react-alert	9.0.1-0	9.0.2-0
@fluentui/react-avatar	9.11.5	9.11.6
@fluentui/react-calendar-compat	0.4.5	0.4.6
@fluentui/react-charts	9.3.24	9.3.25
@fluentui/react-components	9.74.6	9.74.7
@fluentui/react-datepicker-compat	0.6.36	0.6.37
@fluentui/react-dialog	9.18.3	9.18.4
@fluentui/react-drawer	9.13.2	9.13.3
@fluentui/react-icons-compat	0.2.22	0.2.23
@fluentui/react-infobutton	9.0.0-beta.119	9.0.1-0
@fluentui/react-infolabel	9.4.24	9.4.25
@fluentui/react-list	9.6.17	9.6.18
@fluentui/react-menu	9.25.3	9.25.4
@fluentui/react-menu-grid-preview	0.5.5	0.5.6
@fluentui/react-message-bar	9.7.5	9.7.6
@fluentui/react-migration-v0-v9	9.6.35	9.6.36
@fluentui/react-migration-v8-v9	9.10.17	9.10.18
@fluentui/react-motion	9.16.2	9.16.3
@fluentui/react-motion-components-preview	0.15.7	0.15.8
@fluentui/react-nav	9.4.4	9.4.5
@fluentui/react-overflow	9.9.2	9.9.3
@fluentui/react-persona	9.7.7	9.7.8
@fluentui/react-popover	9.14.6	9.14.7
@fluentui/react-portal-compat	9.2.45	9.2.46
@fluentui/react-progress	9.5.4	9.5.5
@fluentui/react-rating	9.4.4	9.4.5
@fluentui/react-swatch-picker	9.6.0	9.6.1
@fluentui/react-table	9.19.19	9.19.20
@fluentui/react-tag-picker	9.10.2	9.10.3
@fluentui/react-tags	9.9.4	9.9.5
@fluentui/react-teaching-popover	9.7.4	9.7.5
@fluentui/react-timepicker-compat	0.4.38	0.4.39
@fluentui/react-toast	9.8.2	9.8.3
@fluentui/react-tree	9.16.5	9.16.6

Not included: release tags

Release git tags are intentionally not recreated. This commit is not the commit the release was built from, so tags pointing at it would misrepresent history, and a single v9 release spans dozens of packages. Tags are not load-bearing for consumers - npm is what they install from.

Follow-up required

The underlying cause is the GitHub credential used by the release pipeline. Until the PAT in the Github and NPM secrets variable group is rotated/fixed, the next release will fail in exactly the same way.

[github-actions]

📊 Bundle size report

✅ No changes found

[github-actions]

Pull request demo site: URL

[Martin Hochel (Hotell)]

good catch, this is definitely wrong !

this is correct, and it's recording a (bad) release rather than causing one.

9.0.1-0 was actually published:

@fluentui/react-infobutton@9.0.1-0 published 2026-08-24T08:16:14Z
@fluentui/react-alert@9.0.2-0 published 2026-08-24T08:16:30Z

Why the version fell off the beta line

Not a beachball v3 bug — a config gap that beachball's downgrade heuristic exposes.

These packages carry "disallowedChangeTypes": ["major", "minor", "patch"] and have no change files of their own; they're bumped as dependents of react-popover etc., where the default dependentChangeType is patch. Beachball resolves a disallowed type by stepping exactly one notch down its ordered list:

SortedChangeTypes = ['none','prerelease','prepatch','patch','preminor','minor','premajor','major']

So patch → prepatch

semver.inc('9.0.0-beta.119', 'prepatch')   -> 9.0.1-0          <- what happened
semver.inc('9.0.0-beta.119', 'prerelease') -> 9.0.0-beta.120   <- what we wanted

Recovery/fix e881bc5

FYI Elizabeth Craig (@ecraig12345)