[23.7] Packages: Recover July 29 npm release metadata

[ciampo]

Companion to #81303.
Follow-up to #80334.

What?

Restores the July 29, 2026 npm package release metadata on release/23.7.

This updates all 121 package versions, their changelogs, and the matching workspace entries in package-lock.json. It does not change the Gutenberg plugin version.

Why?

The Gutenberg 23.7 RC1 package job stopped during npm authentication checks. The packages were later published from commit 7e8b17a983f9391d3ebc7717af2a1c9ed7efc7ab, but the finalization step did not backport the release metadata or create the package tags.

The 23.7 release branch therefore still describes the previous npm package release.

How?

Uses the exact July 29 release sections prepared on wp/latest and the exact versions published to npm. Existing release history and all other package metadata remain unchanged.

This PR does not republish any npm packages or create tags.

Testing Instructions

1. Confirm packages/ui/package.json uses version 0.19.0.
2. Confirm packages/ui/CHANGELOG.md contains 0.19.0 (2026-07-29).
3. Confirm the root versions in package.json and package-lock.json remain unchanged.
4. Run npm run lint:pkg-json.

Additional verification

A focused consistency check verified all 121 packages:

• each manifest changes only its package version;
• each package version matches its lockfile workspace entry;
• each July 29 section matches the prepared release;
• existing release history is unchanged;
• only the expected 243 files changed;
• git diff --check passes.

The full package-json lint was unavailable in the preparation worktree because dependencies were not installed.

Use of AI Tools

Codex was used to investigate the failed release, prepare the metadata recovery, and run the focused consistency checks. The resulting diff and recovery decisions were reviewed by the author.

[github-actions]

Size Change: 0 B

Total Size: 7.76 MB

_{compressed-size-action}