Packages: Backport the September 10 npm release metadata to trunk

[t-hamano]

• Previous: Packages: Recover August 26 npm release metadata #82085
• See: https://wordpress.slack.com/archives/C02QB2JS7/p1789002917561329?thread_ts=1788999002.653179&cid=C02QB2JS7

What?

The trunk half of #82708. The npm publication for the September 10 release succeeded, but the Publish WordPress packages to npm job failed at its final backport step, so trunk never received the release commits. See #82708 for the job output and the wider context.

Why?

trunk still carries the previous package versions, and its changelogs never record the versions that shipped. The next release would compute its version bumps from that stale base.

How?

Cherry-picks the same two commits from wp/latest:

• c89dd70 — Update changelog files
• 485f42a — chore(release): publish

Unlike release/24.0, this needed manual resolution, because several PRs merged during the publication window.

Testing Instructions

Check the changelog diffs in the Files changed tab. 117 of the 121 packages add nothing but a dated version heading directly under ## Unreleased:

 ## Unreleased

+## 2.55.0 (2026-09-10)
+
 ## 2.54.0 (2026-08-26)

Use of AI Tools

Claude Code (Claude Opus 5) resolved the conflicts, moved the misfiled entries, and verified the result against wp/latest and the npm registry. I reviewed the result and take responsibility for it.

🤖 Generated with Claude Code

[github-actions]

🤖 PR meta 🤖

📦 Bundle size

Size Change: 0 B

Total Size: 8.07 MB

_{87774d4 Run}

⚡ Performance

Show the results

Client side metrics exclude the server response time.

front-end-block-theme

Metric	3ececf8	trunk	% Change
timeToFirstByte	55.9 ms +11.54% -1.61%	58.75 ms +6.38% -3.83%	-4.85%
largestContentfulPaint	98 ms +4.08% -8.16%	94 ms +6.38% -2.13%	4.26%
lcpMinusTtfb	34.65 ms +27.99% -3.75%	34.75 ms +10.22% -4.89%	-0.29%
wpBeforeTemplate	27.79 ms +7.09% -0.4%	28.53 ms +11.43% -1.26%	-2.59%
wpTemplate	24.34 ms +4.48% -3.12%	25.05 ms +3.23% -4.35%	-2.83%
wpTotal	52.32 ms +11.1% -1.74%	54.76 ms +7.16% -3.47%	-4.46%
wpMemoryUsage	7.53 MB +0% -0%	7.49 MB +0% -0%	0.46%
wpDbQueries	17 +0% -0%	17 +0% -0%	0%

front-end-classic-theme

Metric	3ececf8	trunk	% Change
timeToFirstByte	39.5 ms +5.7% -1.52%	40.25 ms +5.47% -1.49%	-1.86%
largestContentfulPaint	88 ms +4.55% -0%	88 ms +2.27% -0%	0%
lcpMinusTtfb	49.1 ms +1.32% -1.32%	48 ms +0.83% -0.94%	2.29%
wpBeforeTemplate	26.33 ms +1.79% -1.67%	26.86 ms +4.62% -1.97%	-1.97%
wpTemplate	10.24 ms +2.15% -1.46%	10.58 ms +1.89% -2.27%	-3.21%
wpTotal	36.53 ms +5.56% -1.23%	37.47 ms +5.84% -1.63%	-2.51%
wpMemoryUsage	5.41 MB +0% -0%	5.37 MB +0% -0%	0.65%
wpDbQueries	10 +0% -0%	10 +0% -0%	0%

media-processing

Metric	3ececf8	trunk	% Change
mediaProcessingJpeg	397.15 ms +1.42% -0.74%	397.78 ms +1.32% -0.71%	-0.16%
mediaProcessingAvif	6066.93 ms +0.68% -0.02%	6085.21 ms +0.18% -0.08%	-0.3%
mediaProcessingJpegToAvif	4221.09 ms +0.13% -0.12%	4203.75 ms +0.04% -0.21%	0.41%

media-upload

Metric	3ececf8	trunk	% Change
jpegUploadProcessing	1416.15 ms +36.36% -0.65%	1425.72 ms +0.33% -0.4%	-0.67%
pngUploadProcessing	204.26 ms +5.19% -3.75%	217.77 ms +2.22% -4.32%	-6.2%
largeJpegUploadProcessing	1415.17 ms +0.25% -1.25%	1419.35 ms +1.14% -0.75%	-0.29%
multipleImageUploadProcessing	1564.1 ms +0.27% -1.5%	2064.5 ms +1.21% -6.1%	-24.24%

post-editor

Metric	3ececf8	trunk	% Change
serverResponse	535 ms +5.49% -5%	509.18 ms +3.9% -3.07%	5.07%
firstPaint	253.16 ms +5.82% -12.96%	228.01 ms +16.58% -15.71%	11.03%
domContentLoaded	1353.06 ms +1.56% -0.92%	1309.35 ms +3.29% -1.74%	3.34%
loaded	1354.45 ms +1.55% -0.93%	1310.71 ms +3.3% -1.74%	3.34%
firstContentfulPaint	454.03 ms +4.62% -0.63%	436.47 ms +2.69% -2.92%	4.02%
firstBlock	3707.85 ms +1.88% -0.85%	3609.96 ms +1.12% -0.35%	2.71%
type	15.71 ms +15.47% -6.37%	15.59 ms +9.3% -7.06%	0.77%
typeWithoutInspector	15.22 ms +4.8% -10.71%	15.48 ms +20.54% -7.04%	-1.68%
typeWithTopToolbar	19.87 ms +2.32% -11.52%	18.88 ms +7.52% -2.54%	5.24%
typeContainer	9.01 ms +17.54% -9.1%	9.69 ms +16.72% -2.17%	-7.02%
focus	86.36 ms +12.23% -3.54%	95.03 ms +7.19% -20.33%	-9.12%
firstFocus	183.5 ms +0% -0%	218.66 ms +0% -0%	-16.08%
selectAll	582.02 ms +4.43% -0.65%	602.05 ms +1.84% -0.98%	-3.33%
listViewOpen	74.11 ms +19.13% -12.27%	70.74 ms +10.53% -7.41%	4.76%
inserterOpen	22.51 ms +9.42% -5.86%	23.52 ms +5.19% -9.44%	-4.29%
inserterHover	3.73 ms +16.35% -8.85%	4.04 ms +6.44% -7.67%	-7.67%
inserterSearch	8 ms +8% -5.87%	7.42 ms +2.43% -4.31%	7.82%
loadPatterns	641.23 ms +1.34% -5.18%	657.37 ms +5.77% -3.32%	-2.46%
wpTotal	525.21 ms +5.47% -5.21%	499.24 ms +4.04% -3.1%	5.2%
wpMemoryUsage	13.06 MB +0% -0%	13.03 MB +0% -0%	0.28%
wpDbQueries	54 +0% -1.85%	54 +0% -1.85%	0%

site-editor

Metric	3ececf8	trunk	% Change
serverResponse	287.66 ms +4.65% -2.53%	285.67 ms +2.42% -5.33%	0.7%
firstPaint	181.06 ms +67.17% -20.67%	153.97 ms +6.88% -6.66%	17.59%
domContentLoaded	944.54 ms +1.66% -2.34%	930.34 ms +3.06% -2.18%	1.53%
loaded	945.44 ms +1.67% -2.35%	931.19 ms +3.06% -2.19%	1.53%
firstContentfulPaint	303.45 ms +5.59% -0.41%	302.91 ms +1.23% -0.31%	0.18%
firstBlock	2960.46 ms +0.94% -0.92%	2951.73 ms +2.09% -0.77%	0.3%
type	12.48 ms +3.45% -6.09%	11.93 ms +3.6% -3.6%	4.61%
navigate	80.28 ms +4.2% -16.58%	73.9 ms +5.39% -7.51%	8.63%
loadPatterns	914.87 ms +13.35% -6.39%	939.96 ms +9.75% -7.09%	-2.67%
loadPages	1020.46 ms +5.78% -2.86%	983.32 ms +1.39% -0.96%	3.78%
wpTotal	280.28 ms +4.98% -2.51%	278.7 ms +2.41% -5.53%	0.57%
wpMemoryUsage	12.07 MB +0% -0%	12.04 MB +0% -0%	0.3%
wpDbQueries	43.5 +1.15% -1.15%	43.5 +1.15% -1.15%	0%

_{87774d4 Run}

[t-hamano]

This corrects changelog entries that #79584 added by mistake. All six already appear once under 17.1.0 above.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @gutenbergplugin.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Unlinked contributors: gutenbergplugin.

Co-authored-by: t-hamano <wildworks@git.wordpress.org>
Co-authored-by: ciampo <mciampini@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[ciampo]

@t-hamano I pushed a few fixes to move some entries under the UNRELEASED sections.

I'll do one more rebase, then merge

[t-hamano]

@ciampo Thank you!

[ciampo]

Checks including linting and building all passed, I'm going to merge this PR to prevent more conflicts to happen

[ciampo]

Also added the Require PR update label, which will force all open PR to rebase / merge trunk.