Skip to content

Release: Prerelease 10.5.0-alpha.3#34879

Open
github-actions[bot] wants to merge 96 commits into
next-releasefrom
version-non-patch-from-10.5.0-alpha.2
Open

Release: Prerelease 10.5.0-alpha.3#34879
github-actions[bot] wants to merge 96 commits into
next-releasefrom
version-non-patch-from-10.5.0-alpha.2

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented May 22, 2026

This is an automated pull request that bumps the version from 10.5.0-alpha.2 to 10.5.0-alpha.3.
Once this pull request is merged, it will trigger a new release of version 10.5.0-alpha.3.
If you're not a core maintainer with permissions to release you can ignore this pull request.

To do

Before merging the PR, there are a few QA steps to go through:

  • Add the "freeze" label to this PR, to ensure it doesn't get automatically forced pushed by new changes.
  • Add the "ci:daily" label to this PR, to trigger the full test suite to run on this PR.

And for each change below:

  1. Ensure the change is appropriate for the version bump. E.g. patch release should only contain patches, not new or de-stabilizing features. If a change is not appropriate, revert the PR.
  2. Ensure the PR is labeled correctly with one of: "BREAKING CHANGE", "feature request", "bug", "maintenance", "dependencies", "documentation", "build", "unknown".
  3. Ensure the PR title is correct, and follows the format "[Area]: [Summary]", e.g. "React: Fix hooks in CSF3 render functions". If it is not correct, change the title in the PR.
    • Areas include: React, Vue, Core, Docs, Controls, etc.
    • First word of summary indicates the type: “Add”, “Fix”, “Upgrade”, etc.
    • The entire title should fit on a line

This is a list of all the PRs merged and commits pushed directly to next, that will be part of this release:

  • 🐛 Bug: Controls: Add label to Object JSON control #34766
  • ✨ Feature Request: CLI: Respect BROWSER and BROWSER_ARGS #34513
  • 🐛 Bug: UI: Allow manager-head favicon override #34809
  • 🐛 Bug: Core: Fix EEXIST race condition in static file copying during build #34499
  • 🐛 Bug: Core: Incorrect package json handling #34515
  • 🐛 Bug: Addon-Docs: Resolve providerImportSource to a path instead of a file:// URL #34841
  • 🐛 Bug: Core: Improve ActionBar focus indicator in high contrast mode #34779
  • ✨ Feature Request: Core: Add runtime instance registry #34863
  • 🐛 Bug: Core: Categorize UniversalStore follower timeout error #34592
  • 📦 Dependencies: Add an optional TypeScript peer to react-vite #34627
  • 🐛 Bug: A11y-Addon: Preserve disabled a11y rules with runOnly #34649
  • ✨ Feature Request: CSF-Next: Add tags type support for #34819
  • 🐛 Bug: Addon-Docs: Resolve CSF4 module exports without a default export #34834
  • 📦 Dependencies: Build: Upgrade type-fest to latest version 5.6.0 #34791 (will also be patched)
  • 🏗️ Build: Build: Persist root node_modules to the CI workspace #34886
  • 🏗️ Build: AgentScan: Move label map to agent-san parameters #34885
  • 🏗️ Build: Security: Implement stricter rules for CircleCI cache writes #34853
  • 📝 Documentation: Docs: Add Code Authoring Principles for agents #34835

If you've made any changes doing the above QA (change PR titles, revert PRs), manually trigger a re-generation of this PR with this workflow and wait for it to finish. It will wipe your progress in this to do, which is expected.

Feel free to manually commit any changes necessary to this branch after you've done the last re-generation, following the Make Manual Changes section in the docs, especially if you're making changes to the changelog.

When everything above is done:


Generated changelog

10.5.0-alpha.3

  • A11y-Addon: Preserve disabled a11y rules with runOnly - #34649, thanks cyphercodes!
  • Add an optional TypeScript peer to react-vite - #34627, thanks wojtekmaj!
  • Addon-Docs: Resolve CSF4 module exports without a default export - #34834, thanks TheSeydiCharyyev!
  • Addon-Docs: Resolve providerImportSource to a path instead of a file:// URL - #34841, thanks TheSeydiCharyyev!
  • Build: Upgrade type-fest to latest version 5.6.0 - #34791, thanks tobiasdiez!
  • CLI: Respect BROWSER and BROWSER_ARGS - #34513, thanks ianzone!
  • CSF-Next: Add tags type support for - #34819, thanks unional!
  • Controls: Add label to Object JSON control - #34766, thanks Jaksenc!
  • Core: Add runtime instance registry - #34863, thanks kasperpeulen!
  • Core: Categorize UniversalStore follower timeout error - #34592, thanks justismailmemon!
  • Core: Fix EEXIST race condition in static file copying during build - #34499, thanks flt3150sk!
  • Core: Improve ActionBar focus indicator in high contrast mode - #34779, thanks TheSeydiCharyyev!
  • Core: Incorrect package json handling - #34515, thanks lino-levan!
  • UI: Allow manager-head favicon override - #34809, thanks MukundaKatta!

flt3150sk and others added 30 commits April 8, 2026 20:00
Add `force: true` to all `fs.cp()` calls in the static build pipeline.
The preview build (Vite) and static file copies run in parallel via
`Promise.all`, which can cause EEXIST errors when both attempt to create
the same subdirectory simultaneously — especially on CI runners with
slow I/O.
pass correct option to open()
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
When a bundler splits a CSF4 story module (no `export default meta`)
into a separate chunk, the namespace object passed to `<Meta of={...} />`
differs by object identity from the one Storybook registered. The
existing default-export fallback in `DocsContext.resolveModuleExport`
cannot handle this case because CSF4 modules have no `default` key.

Fall back to identifying the CSF file via any of its story exports.
Reject the lookup when story exports span multiple CSF files. Guard
against individual CSF4 Story objects so `<Canvas of={Stories.Primary} />`
keeps resolving to a story.

Fixes #34159
Fixes #34373
Distilled from recurring failure modes in agent-authored PRs: comments as
investigation transcript, bending production to the test harness, unproven
environment assumptions, over-engineered defensive tests, convention drift in
generated files, and speculative generality.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Use ">= 4.9.x" (matching @storybook/react-webpack5 and the react
renderer) instead of ">=4.9.x", and refresh yarn.lock.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sidnioulz and others added 2 commits May 22, 2026 14:20
@storybook-bot storybook-bot force-pushed the version-non-patch-from-10.5.0-alpha.2 branch from cb7bacf to ce6f36c Compare May 22, 2026 12:22
…json-handling

Core: Incorrect package json handling
@storybook-bot storybook-bot force-pushed the version-non-patch-from-10.5.0-alpha.2 branch from ce6f36c to ccac1b7 Compare May 22, 2026 12:36
…atic-copy

Core: Fix EEXIST race condition in static file copying during build
@storybook-bot storybook-bot force-pushed the version-non-patch-from-10.5.0-alpha.2 branch from ccac1b7 to 4e8bbc6 Compare May 22, 2026 13:03
@storybook-bot storybook-bot force-pushed the version-non-patch-from-10.5.0-alpha.2 branch from 4e8bbc6 to dfb9ced Compare May 22, 2026 13:40
Sidnioulz and others added 7 commits May 22, 2026 15:47
CircleCI downstream jobs received the workspace-root node_modules --
where Yarn hoists shared/singleton deps like oxc-parser, vitest and
type-fest -- only via the shared save_cache, which is gated on
isTrustedAuthor(). Community/fork PRs therefore ran with freshly-built
dist output but no root node_modules, causing failures unrelated to
their diff (e.g. "Cannot find package 'oxc-parser'", "command not
found: vitest", stale type-fest typecheck errors).

Persist node_modules, code/node_modules and scripts/node_modules to the
pipeline-scoped workspace in build_linux, and attach the workspace after
restoring the cache so the fresh build output is authoritative.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…f needed

Agent-Logs-Url: https://github.com/storybookjs/storybook/sessions/261ad771-2035-454b-b268-561ccbdd8c2c

Co-authored-by: Sidnioulz <5108577+Sidnioulz@users.noreply.github.com>
AgentScan: Move label map to agent-san parameters
@storybook-bot storybook-bot force-pushed the version-non-patch-from-10.5.0-alpha.2 branch from dfb9ced to 32ef771 Compare May 22, 2026 14:23
Copilot AI and others added 3 commits May 22, 2026 14:24
Agent-Logs-Url: https://github.com/storybookjs/storybook/sessions/261ad771-2035-454b-b268-561ccbdd8c2c

Co-authored-by: Sidnioulz <5108577+Sidnioulz@users.noreply.github.com>
CLI: Respect BROWSER and BROWSER_ARGS
Controls: Add label to Object JSON control
@storybook-bot storybook-bot force-pushed the version-non-patch-from-10.5.0-alpha.2 branch from 32ef771 to a54d062 Compare May 22, 2026 14:28
Sidnioulz and others added 2 commits May 22, 2026 17:17
@storybook-bot storybook-bot force-pushed the version-non-patch-from-10.5.0-alpha.2 branch from a54d062 to 5fca923 Compare May 22, 2026 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release For PRs that trigger new releases. Automated

Projects

None yet

Development

Successfully merging this pull request may close these issues.