Repository navigation
Release: Prerelease 11.0.0-alpha.7 - #36743
Open
github-actions[bot] wants to merge 594 commits into
Open
github-actions[bot] wants to merge 594 commits into
github-actions[bot] wants to merge 594 commits into
Conversation
github-actions
Bot
added
the
release
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 22da308d87
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| } | ||
|
|
||
| // We don't only merge at the very top level (the same way as React setState) | ||
| // TODO: Remove in SB 12 |
There was a problem hiding this comment.
For users upgrading directly from 10.3 to 11, this only removes the tag filters from the in-memory read; it never deletes them from local storage, and subsequent persistent updates retain them because update() merges the previous record. If the omit is removed in SB 12 as instructed here, those users' stale includedTagFilters and excludedTagFilters will be merged back into initial state during the supported 11→12 upgrade, unexpectedly restoring old filters and combining them with URL-derived values. Keep this exclusion permanent, or clear the legacy keys during SB 11 before scheduling its removal.
Useful? React with 👍 / 👎.
Contributor
Author
|
storybook-bot
force-pushed
the
version-non-patch-from-11.0.0-alpha.6
branch
from
October 12, 2026 19:28
22da308 to
a0a6567
Compare
storybook-bot
requested review from
jonniebigodes and
kylegach
as code owners
October 12, 2026 19:28
storybook-bot
force-pushed
the
version-non-patch-from-11.0.0-alpha.6
branch
11 times, most recently
from
October 13, 2026 13:47
b40a850 to
e61e0fe
Compare
New colocated vitest suite for normalizeArgType: no-toolbar input
returns null, string items become { value, title }, a reset item
inherits the toolbar icon and clears its value, a reset item passes
through without an icon, user name/description pass through untouched,
and items receive no injected defaults.
A satisfies GlobalTypes fixture pins the minimal entry shape and an
@ts-expect-error fixture proves an undocumented extra key in a
globalTypes toolbar entry fails typecheck.
Add an 11.0 section for the removed index signature (extra keys in globalTypes toolbar entries now error) and the removed defaultValue field (use initialGlobals). Update the argTypes defaultValue section, which previously claimed globalTypes.defaultValue was unchanged.
The angular-cli-latest--webpack---typescript---dev job failed on the previous head while passing on an identical codebase (the only delta is a svelte test fixture no runtime consumes).
storybook-bot
force-pushed
the
version-non-patch-from-11.0.0-alpha.6
branch
from
October 13, 2026 14:07
e61e0fe to
abd6e02
Compare
Storybook 11 no longer reads the CSF v1 Story.story bag. Put each field on the story itself. The CSF 2-to-3 codemod still expands a static bag, because the indexer used to do that for it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…n-a11y Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
react@beta on npm is still the May 2024 19.0 beta. Storybook 11 already works with React 19.3, so these sandboxes should track react@canary. @types/react has no canary tag, so the type pins now use @types/react@latest and @types/react-dom@latest instead of the unscoped types-react beta packages.
svelte-vite uses the TypeScript compiler API for docgen at runtime. TypeScript 7.0.x no longer ships that API, so the direct dependency must stay at ^5.9.0 || ^6.0.0 even though the peer range widens to accept TS 7 in consumer projects (where the peer range does not govern svelte-vite's own compiler). Co-authored-by: Gert Hengeveld <gert@chromatic.com>
…-failure CLI: Exit 1 when the add command's setup fails
…e-race Core: Load presets sequentially to prevent ESM require() race in CJS presets
storybook-bot
force-pushed
the
version-non-patch-from-11.0.0-alpha.6
branch
from
October 19, 2026 12:07
fce6d83 to
8399bf1
Compare
TanStack: Support Render-Prop Children in Link Mock
…ii-path Vitest: Decode non-ASCII characters in file paths for test execution guard
storybook-bot
force-pushed
the
version-non-patch-from-11.0.0-alpha.6
branch
from
October 19, 2026 12:57
8399bf1 to
0081a74
Compare
…anel Manager: Keep addon panel filter active before a story is prepared
storybook-bot
force-pushed
the
version-non-patch-from-11.0.0-alpha.6
branch
from
October 19, 2026 13:08
0081a74 to
255fb18
Compare
…liases Core: Remove deprecated CSF and manager type aliases [SB-2017]
storybook-bot
force-pushed
the
version-non-patch-from-11.0.0-alpha.6
branch
from
October 19, 2026 13:13
255fb18 to
95c2a26
Compare
CLI: Keep msw-storybook-addon v2 during automigration
storybook-bot
force-pushed
the
version-non-patch-from-11.0.0-alpha.6
branch
from
October 19, 2026 13:29
95c2a26 to
cfed85b
Compare
Windows: Fix various FS-related test failures
…ndboxes Sandboxes: Pin React prerelease templates to canary
storybook-bot
force-pushed
the
version-non-patch-from-11.0.0-alpha.6
branch
from
October 19, 2026 13:39
cfed85b to
8a5be09
Compare
CLI: Use pnpm to query the registry URL
storybook-bot
force-pushed
the
version-non-patch-from-11.0.0-alpha.6
branch
from
October 19, 2026 14:08
8a5be09 to
544539b
Compare
- Pass the full Storybook coverage options at startup and vary only `enabled`, so `enableCoverage()` reports through the Storybook reporter into the cache dir. - Give the coverage reporter a `getTestManager` function instead of the manager. Vitest deep-clones coverage options on a runtime toggle, which would otherwise hand the reporter a disconnected copy. - Add `setCoverage()`: waits for a pending restart, cancels the current run, then toggles. Coverage state is tracked on the manager because `vitest.config.coverage.enabled` does not follow `disableCoverage()`. - Exclude the coverage browser modules from dependency optimization. Vitest only does this when coverage is enabled at startup; otherwise Vite optimizes them mid-run and reloads the tests. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Addon Vitest: Toggle coverage without restarting Vitest
storybook-bot
force-pushed
the
version-non-patch-from-11.0.0-alpha.6
branch
from
October 19, 2026 16:17
544539b to
8484694
Compare
…or-interop Vue3: Support Vapor components through Vue's interop plugin
storybook-bot
force-pushed
the
version-non-patch-from-11.0.0-alpha.6
branch
from
October 19, 2026 16:46
8484694 to
6f394f5
Compare
Frameworks: Accept TypeScript 7 in peer dependency ranges
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
16 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is an automated pull request that bumps the version from `11.0.0-alpha.6` to `11.0.0-alpha.7`.
Once this pull request is merged, it will trigger a new release of version `11.0.0-alpha.7`.
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:
And for each change below:
This is a list of all the PRs merged and commits pushed directly to `next`, that will be part of this release:
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
11.0.0-alpha.7