Build: Update next with changes from main
#27123
Merged
Conversation
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
Co-authored-by: Jeppe Reinhold <[email protected]>
Docs: Add `svelte-webpack5` framework doc
Docs: Add `vue3-webpack5` framework doc
…ts-vite Docs: Add `web-components-vite` framework doc
…ts-webpack5 Docs: Add `web-components-webpack5` framework doc
Co-authored-by: Jeppe Reinhold <[email protected]>
- Mark features as experimental - Update types
Docs: Add `sveltekit` framework doc
- Same changes as in #26401, targeting `main`
…t-docs-homepage-latest Docs: Add get started index (latest)
Docs: Fix get started (latest)
Docs: Fix get started 2 (latest)
Docs: Fix heading levels of `useOf` API reference (cherry picked from commit 85adf5a)
Build: Fix the test-runner-prod step (cherry picked from commit 479b8e9)
React: Support v19 in `react-dom-shim` (cherry picked from commit 34f0c20)
…tsinclude Vite: Merge assetsInclude property with Storybook default values (cherry picked from commit f6ecc28)
…e-fonts Sandboxes: Fix inconsistent monospace fonts in Chromatic (cherry picked from commit 9148b6a)
Release: Patch 8.0.10
…nflicts resolved to ours [skip ci]
…com/storybookjs/storybook into version-non-patch-from-8.1.0-beta.1
….0-beta.1 Release: Minor 8.1.0
☁️ Nx Cloud ReportCI is running/has finished running commands for commit fd21fc0. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 2 targetsSent with 💌 from NxCloud. |
ndelangen
changed the title
next with changes from mainnext with changes from main
5 tasks
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.
What I did
Update the
nextbranch, by merging the changes frommaininto it.Checklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!
Documentation
MIGRATION.MD
Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal,ci:mergedorci:dailyGH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli/src/sandbox-templates.tsMake sure this PR contains one of the labels below:
Available labels
bug: Internal changes that fixes incorrect behavior.maintenance: User-facing maintenance tasks.dependencies: Upgrading (sometimes downgrading) dependencies.build: Internal-facing build tooling & test updates. Will not show up in release changelog.cleanup: Minor cleanup style change. Will not show up in release changelog.documentation: Documentation only changes. Will not show up in release changelog.feature request: Introducing a new feature.BREAKING CHANGE: Changes that break compatibility in some way with current major version.other: Changes that don't fit in the above categories.🦋 Canary release
This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the
@storybookjs/coreteam here.core team members can create a canary release here or locally with
gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>