Release: Prerelease 10.3.0-alpha.5#33812
Merged
valentinpalkovic merged 7 commits intoFeb 10, 2026
Merged
Conversation
…uilds The vite-inject-mocker plugin injects a `<script>` tag with an absolute path (`/vite-inject-mocker-entry.js`) into the HTML. When the built Storybook is hosted under a non-root base path (e.g. GitHub Pages at `/my-repo/`), the browser resolves the absolute URL against the host root, resulting in a 404. The fix switches to a relative path (`./vite-inject-mocker-entry.js`) during production builds while keeping the absolute path in dev mode (where Vite's dev-server needs it for `resolveId` matching). This is consistent with other assets in `iframe.html` which already use relative paths (e.g. `./sb-common-assets/…`). Fixes #32428 Co-authored-by: Cursor <cursoragent@cursor.com>
…event race condition
…ls-race-condition Viewport: Skip viewport validation before parameters load
…ative-path Builder-Vite: Use relative path for mocker entry in production builds
github-actions
Bot
requested review from
jonniebigodes and
kylegach
as code owners
valentinpalkovic
added
freeze
|
View your CI Pipeline Execution ↗ for commit bc5bcd0
☁️ Nx Cloud last updated this comment at |
Package BenchmarksCommit: The following packages have significant changes to their size or dependencies:
|
| Before | After | Difference | |
|---|---|---|---|
| Dependency count | 103 | 92 | 🎉 -11 🎉 |
| Self size | 1.12 MB | 1.12 MB | 🚨 +18 B 🚨 |
| Dependency size | 22.60 MB | 21.16 MB | 🎉 -1.44 MB 🎉 |
| Bundle Size Analyzer | Link | Link |
@storybook/react-native-web-vite
| Before | After | Difference | |
|---|---|---|---|
| Dependency count | 135 | 124 | 🎉 -11 🎉 |
| Self size | 30 KB | 30 KB | 🎉 -18 B 🎉 |
| Dependency size | 23.89 MB | 22.45 MB | 🎉 -1.44 MB 🎉 |
| Bundle Size Analyzer | Link | Link |
@storybook/react-vite
| Before | After | Difference | |
|---|---|---|---|
| Dependency count | 93 | 82 | 🎉 -11 🎉 |
| Self size | 35 KB | 35 KB | 0 B |
| Dependency size | 20.39 MB | 18.94 MB | 🎉 -1.44 MB 🎉 |
| Bundle Size Analyzer | Link | Link |
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
4 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.4to10.3.0-alpha.5.Once this pull request is merged, it will trigger a new release of version
10.3.0-alpha.5.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.5