Storybook: Upgrade to 10.5

[aduth]

What?

Upgrades Storybook from 10.4.3 to 10.5.3.

Relevant changelogs:

• https://github.com/storybookjs/storybook/releases/tag/v10.4.4
• https://github.com/storybookjs/storybook/releases/tag/v10.4.5
• https://github.com/storybookjs/storybook/releases/tag/v10.4.6
• https://github.com/storybookjs/storybook/releases/tag/v10.5.0
• https://github.com/storybookjs/storybook/releases/tag/v10.5.1
• https://github.com/storybookjs/storybook/releases/tag/v10.5.2
• https://github.com/storybookjs/storybook/releases/tag/v10.5.3

Temporarily merges to #80655, in order to demonstrate regression coverage success, and an expectation that #80655 will be merged first and then this rebased against trunk.

Why?

• Improves documentation: Fixes an issue where we previously had to workaround a bug in earlier versions, and improves documentation of some components (see effect on Popover.Slot in storybook/components-manifest.yml)
• Originally the hope here was to take advantage of the new, broadly-available experimental docgen service added in 10.5.0, since we already use it for components manifest and document that we want to align this with the front-end experience. Unfortunately the new option experimentalDocgenServer again changes the format of the manifest in ways that will break our design system MCP client and will need separate reconciliation (see Storybook: Use experimental docgen server #80697). This work will at least serve as an incremental step in that direction.
• Good maintenance hygiene, as drift in versions compounds eventual reconciliation cost.

Testing Instructions

Verify that Storybook builds and loads with expected documentation, and verify that components manifest and its related tests continue as expected. To verify this, follow testing instructions from #80655.

Use of AI Tools

Used Cursor IDE + Auto (like Composer) model to navigate the upgrade and effect on components manifests, reviewed and iterated manually.

[github-actions]

Size Change: 0 B

Total Size: 7.77 MB

_{compressed-size-action}

[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.

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

Co-authored-by: aduth <aduth@git.wordpress.org>
Co-authored-by: mirka <0mirka00@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.

[aduth]

• Originally the hope here was to take advantage of the new, broadly-available experimental docgen service added in 10.5.0, since we already use it for components manifest and document that we want to align this with the front-end experience. Unfortunately the new option experimentalDocgenServer again changes the format of the manifest in ways that will break our design system MCP client and will need separate reconciliation (draft PR coming soon). This work will at least serve as an incremental step in that direction.

I've opened a draft pull request to demonstrate what the issues we'll encounter looks like: #80697

[github-actions]

Flaky tests detected in 7ed2af3.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/32482007545
📝 Reported tests:

shows pattern summary fields in the post editor in /test/e2e/specs/editor/various/post-summary.spec.js, passed after 1 failed attempt.

Error: apiRequestContext.fetch: socket hang up
Call log:
  - → GET http://localhost:8889/wp-json/wp/v2/blocks?per_page=100&status=publish%2Cfuture%2Cdraft%2Cpending%2Cprivate%2Ctrash
    - user-agent: Playwright/1.62.1 (x64; ubuntu 24.04) node/20.20 CI/1
    - accept: */*
    - accept-encoding: gzip,deflate,br
    - X-WP-Nonce: 97e39ec58d
    - cookie: wordpress_test_cookie=WP%20Cookie%20check; wordpress_logged_in_23778236db82f19306f247e20a353a99=admin%7C1787489351%7CBZhoc6r4PEH1KexYVp8LubJqR5FJE8yqVuh1yREwJ37%7Cf338207339c6bbb00dfe128f98ea9937392577631e0731064c479c032abefdef; wp-settings-time-1=1787317307

    at RequestUtils.rest (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/request-utils/rest.ts:112:39)
    at RequestUtils.deleteAllBlocks (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/request-utils/blocks.ts:23:28)
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/post-summary.spec.js:61:23

[mirka]

Tests well, and the e2e Storybook is also good.

Looks like 10.5.4 is already out, but not a blocker 😄

[ciampo]

Looks like 10.5.4 is already out, but not a blocker 😄

We're at 10.5.10 now, probably a good small targeted follow-up PR after this one merged

[aduth]

Yeah I expect 10.6 is imminent as well. They've got a pretty frequent release cadence these days. Might just end up waiting for that one unless there's something compelling from the patch versions.

[aduth]

Actually it looks like with resolving merge conflicts and using ^ range, the actual effective installed version here is now 10.5.8 (see package-lock.json). It likely skipped 10.5.9 and 10.5.10 because of my min-release-age npm settings at the time of rebase.