Release: Merge patches to main (without version bump)
#33298
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
github-actions
bot
requested review from
jonniebigodes and
kylegach
as code owners
…ment-followup Docs: Follow up on nav experiment (cherry picked from commit 9548e92)
storybook-bot
force-pushed
the
version-patch-from-10.1.4
branch
from
2d2066c to
4fa914e
Compare
github-actions
bot
changed the title
main (without version bump)
shilman
added
ci:daily
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. None of the changes requires a version bump, they are only internal or documentation related. Merging this PR will not trigger a new release, but documentation will be updated.
If you're not a core maintainer with permissions to release you can ignore this pull request.
To do
Before merging the PR:
This is a list of all the PRs merged and commits pushed directly to
nextsince the last release:If you've made any changes (change PR titles, revert PRs), manually trigger a re-generation of this PR with this workflow and wait for it to finish.
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.
When everything above is done: