Release: Prerelease 10.3.0-alpha.4#33761
Merged
valentinpalkovic merged 23 commits intoFeb 4, 2026
Merged
Conversation
Co-authored-by: ia319 <linglingmeng876@gmail.com>
Fixes #27091 When meta defines `argTypes: { prop: { control: false } }`, story-level argTypes with `control: 'text'` or `control: { type: 'select' }` should be able to re-enable the control. The issue was that `control: false` was normalized to `{ disable: true }` and `control: 'text'` was normalized to `{ type: 'text' }`. When merged via combineParameters, both properties were kept, resulting in `{ disable: true, type: 'text' }` which still disabled the control. The fix ensures that when a control type is explicitly specified, the normalized control object includes `disable: false` to override any inherited `disable: true` from parent argTypes. This maintains backward compatibility: - `control: false` still disables controls - `control: { disable: true }` still works - But now `control: 'text'` properly overrides `control: false`
Fixes #21429 In docs mode, the menu tool was rendering a Separator that had no tools following it, causing an orphaned divider to appear in the toolbar. The Separator in menuTool is intended to visually separate the menu button from subsequent tools (like remountTool). However, in docs mode, remountTool and other left-side tools are filtered out by their match function, leaving the separator with nothing to separate. The fix makes the Separator conditional on viewMode === 'story', since that's when the other left-side tools are actually visible.
…m:storybookjs/storybook into jeppe/use-correct-story-name-in-manifests
…a custom condition
Build: No dts-mapper files during dev
Toolbar: Remove extra toolbar divider when zoom controls not shown
…ride-27091 Controls: Allow story argTypes to override control: false from meta
github-actions
Bot
requested review from
jonniebigodes and
kylegach
as code owners
storybook-bot
force-pushed
the
version-non-patch-from-10.3.0-alpha.3
branch
from
c5f8f43 to
6069040
Compare
Manager: Update logic to use base path instead of full pathname
storybook-bot
force-pushed
the
version-non-patch-from-10.3.0-alpha.3
branch
from
6069040 to
3806b58
Compare
…me-in-manifests Manifests: Use correct story name
storybook-bot
force-pushed
the
version-non-patch-from-10.3.0-alpha.3
branch
from
3806b58 to
9148c7c
Compare
…nfig-with-deferred-export Addon-Vitest: Support vite/vitest config with deferred export
storybook-bot
force-pushed
the
version-non-patch-from-10.3.0-alpha.3
branch
from
9148c7c to
9472ef0
Compare
valentinpalkovic
added
ci:daily
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
7 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
10.3.0-alpha.3to10.3.0-alpha.4.Once this pull request is merged, it will trigger a new release of version
10.3.0-alpha.4.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
10.3.0-alpha.4