Release: Prerelease 10.6.0-alpha.9 - #36039
Merged
Merged
Conversation
… when launch/preview helpers are used out of context
Archive ports that only restate 801/802/804/803/810, plus duplicate prompt shapes. Keep async mocks, story drift, tool-param, preview, and vitest-CLI coverage on the latest matrix.
Token-only and other token failures now respond with 401 Unauthorized. Invalid Origin still returns 403 Forbidden. Tests spy on handleUpgrade instead of replacing the method.
destroy() can drop a still-queued 401/403 write, so rejected upgrades now end() the socket after the status line. Real TCP tests cover both statuses.
The angular-vite framework and the angular-to-angular-vite migration both read a Storybook builder target's `zoneless` option, and they disagreed about what its absence means. `resolveZoneless` reads an absent option as zoneless; the migration read the same absence as zone-based and wrote a static `import 'zone.js'` into preview.ts. A target that declares nothing is the common case, and it is exactly what the migration itself writes, so a freshly migrated project landed on the one disagreeing row by construction: the framework excluded zone.js from `optimizeDeps` while the preview imported it anyway. With no `zone.js` dependency that import cannot resolve and every story fails; with one, the app runs zoneless and logs NG0914 on every load. The dependency tree is the signal that survives an option nobody wrote, so the migration now writes the import when the project declares `zone.js`, and warns instead of writing when a target says `zoneless: false` in a project that has no `zone.js` to import. The framework's `?? true` stays as it is - removing the migration's competing default is what makes the two agree.
Each transport starts a heartbeat interval that only clears when the WebSocketServer closes. Tests now call close() so those timers do not leak.
close() is now idempotent and removes the process SIGTERM handler it registered, so tests and repeated construction do not leak listeners.
…ccess The TypeScript 7 package check reports TS2341 on transport.socket. Route those spies through a double assertion so the tests still cover upgrade handling.
…s for agent-driven CLI runs
…mary and ctx.agent
Keep this PR's eval restructure and 9xx deletions. Apply next's renamed workflow tools (docs-show, review-create, stories-preview, test-run).
esbuild minifySyntax was emitting `var TabErrorBoundary = class extends ..., Tabs = memo(...)`. Webpack innerGraph drops the memo binding from that shape, so production Next.js webpack docs throw `memo is not defined`.
…de-token-only-900b Core: Allow token-only WebSocket upgrade without Origin
github-actions
Bot
added
the
release
Typed function params reject the old selected/id null defaults, which also left an unused ts-expect-error.
Make setup requests authorize required upgrades and direct documentation lookups through Storybook before source inspection.
…raph-tabs-memo Core: Keep Tabs memo out of an esbuild joined var
storybook-bot
force-pushed
the
version-non-patch-from-10.6.0-alpha.8
branch
from
August 25, 2026 12:39
ffa7aa3 to
5874371
Compare
Vue: Raise the vue-component-meta floor to ^3.3.9
storybook-bot
force-pushed
the
version-non-patch-from-10.6.0-alpha.8
branch
from
August 25, 2026 18:34
5874371 to
cf24e90
Compare
storybook-bot
force-pushed
the
version-non-patch-from-10.6.0-alpha.8
branch
from
August 26, 2026 08:32
cf24e90 to
89b89be
Compare
Vue: Rearchitecture Story snippet generation
storybook-bot
force-pushed
the
version-non-patch-from-10.6.0-alpha.8
branch
from
August 26, 2026 08:47
89b89be to
0749196
Compare
…system Evals: Clean up and restructure
ndelangen
added
ci:daily
Contributor
Package BenchmarksCommit: The following packages have significant changes to their size or dependencies:
|
| Before | After | Difference | |
|---|---|---|---|
| Dependency count | 94 | 94 | 0 |
| Self size | 32 KB | 32 KB | 🎉 -24 B 🎉 |
| Dependency size | 18.50 MB | 18.52 MB | 🚨 +21 KB 🚨 |
| Bundle Size Analyzer | Link | Link |
@storybook/vue3
| Before | After | Difference | |
|---|---|---|---|
| Dependency count | 90 | 90 | 0 |
| Self size | 161 KB | 181 KB | 🚨 +21 KB 🚨 |
| Dependency size | 18.10 MB | 18.10 MB | 0 B |
| Bundle Size Analyzer | Link | Link |
Vue: Fix setup statement slicing on Windows
storybook-bot
force-pushed
the
version-non-patch-from-10.6.0-alpha.8
branch
from
August 26, 2026 10:32
0749196 to
1bcdcd5
Compare
ndelangen
approved these changes
Aug 26, 2026
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
9 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.6.0-alpha.8` to `10.6.0-alpha.9`.
Once this pull request is merged, it will trigger a new release of version `10.6.0-alpha.9`.
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.6.0-alpha.9