Release: Prerelease 10.5.0-alpha.3#34943
Open
github-actions[bot] wants to merge 183 commits into
Open
Conversation
Co-authored-by: Sidnioulz <5108577+Sidnioulz@users.noreply.github.com>
…prioritize .cmd Co-authored-by: Sidnioulz <5108577+Sidnioulz@users.noreply.github.com>
Co-authored-by: Sidnioulz <5108577+Sidnioulz@users.noreply.github.com>
Co-authored-by: Sidnioulz <5108577+Sidnioulz@users.noreply.github.com>
Co-authored-by: Sidnioulz <5108577+Sidnioulz@users.noreply.github.com>
- Update README to reflect that the onboarding addon is no longer included by default in new Storybook projects - Update telemetry docs to link to the monorepo location instead of the archived addon-onboarding repository Fixes #32530
Add jsdoc explaining the capture-after-merge ordering of recentVisibleSizes, plus inline notes on the unknown-key safety net and the singleStory nav guard. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Fold the `singleStory` nav guard into the `showSidebar === false` branch so the function ends on a single return; equivalent behavior, easier to read. - Add the missing `showPanel: undefined` entry to the default `layoutCustomisations` so it matches `API_LayoutCustomisations`. - Omit `recentVisibleSizes` from `API_LayoutOptions` — it is internal restoration bookkeeping and not something callers should set via `addons.setConfig`. - Note in `API_LayoutOptions` that `showToolbar` already comes from `Partial<API_Layout>` and is intentionally not redeclared. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The `Omit<Partial<API_Layout>, 'recentVisibleSizes'>` introduced in the previous commit breaks the rollup-plugin-dts build of core because `applyLayoutOptions` calls `pick(layoutOptions, layoutKeys)` where `layoutKeys` is typed as `(keyof API_Layout)[]` (includes `recentVisibleSizes`) but the destructured `layoutOptions` no longer accepts it. Reverting to `extends Partial<API_Layout>` restores the type compatibility. The `recentVisibleSizes` field is internal restoration bookkeeping and practically no caller sets it via `addons.setConfig`, so the type-tightening was nice-to-have and not worth the breakage. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…rvice-arch-explorations
…erver"" This reverts commit dce85c3.
…ical-jones-e3d0c1
…-attempt-2 Open-service: Implement service registration on the server (attempt 2)
storybook-bot
force-pushed
the
version-non-patch-from-10.5.0-alpha.2
branch
from
cc84d7d to
913013d
Compare
Patches react-element-to-jsx-string (the @7rulnik fork) with algolia/react-element-to-jsx-string#733, which removes the branch that silently omitted boolean props explicitly set to `false`. React source snippets now render `foo={false}` instead of dropping the prop, while `true` props keep the shorthand syntax. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…d related tests - Updated service definitions to replace `filePath` with `staticPath` for consistency in static file generation. - Adjusted related tests and documentation to reflect the new naming convention. - Ensured all references to `filePath` are updated to maintain functionality and clarity. All tests pass and type checks are clean.
- Removed the LoadCtx parameter from the static input resolution function to streamline the process. - Updated the documentation to clarify the behavior of static inputs in service registration. - Ensured that the function now directly returns the static inputs without additional checks. All tests pass and type checks are clean.
- Enhanced the documentation for the `Query` type to clarify the behavior of the `.subscribe` method. - Updated description to specify that subscribers receive the current value immediately and subsequent updates after the background load settles. All tests pass and type checks are clean.
…nt-to-jsx-string-false-props React: Render boolean props set to false in source snippets
storybook-bot
force-pushed
the
version-non-patch-from-10.5.0-alpha.2
branch
from
913013d to
4cc3965
Compare
…anel Manager: Fix layout.showPanel config
…ed-code AI: Tell agents to preserve generated code unless relevant changes
…-link-cut-off Docs: Prevent heading anchor cutoff on docs pages
- Introduced a new test to verify that dependency loads are not refired during the final evaluation of the `.loaded()` method in service runtime. - Updated service definitions to include a spy for monitoring load calls and ensure correct behavior. - Enhanced documentation in the service runtime to clarify the return behavior of handlers during the final evaluation. All tests pass and type checks are clean.
storybook-bot
force-pushed
the
version-non-patch-from-10.5.0-alpha.2
branch
from
4cc3965 to
15eaa0b
Compare
- Introduced a new test to verify that the `runLoadOnce` method does not duplicate loads when the body synchronously re-reads itself. - Enhanced service definitions to include spies for monitoring load and command calls, ensuring correct behavior during execution. - Updated the service runtime to manage in-flight loads more effectively, preventing unintended duplications. All tests pass and type checks are clean.
- Updated the test for dependency load behavior to utilize a spy on the load method of the service definition, enhancing monitoring of load calls. - Ensured proper restoration of the spy after the test execution to maintain test integrity. - All tests pass and type checks are clean.
Open Service: Sync queries, load/loaded() API, strict reader handlers
storybook-bot
force-pushed
the
version-non-patch-from-10.5.0-alpha.2
branch
from
15eaa0b to
e994133
Compare
CSF Next: Propagate skip tags to .test children
storybook-bot
force-pushed
the
version-non-patch-from-10.5.0-alpha.2
branch
from
e994133 to
f674b3f
Compare
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
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.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:
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.5.0-alpha.3