-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release: Patch 7.6.13 #25843
Merged
Merged
Release: Patch 7.6.13 #25843
Conversation
This file contains 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
kylegach and
jonniebigodes
as code owners
January 31, 2024 16:35
github-actions
bot
added
the
release
For PRs that trigger new releases. Automated
label
Jan 31, 2024
storybook-bot
force-pushed
the
version-patch-from-7.6.12
branch
4 times, most recently
from
January 31, 2024 23:23
f33c52b
to
9ed4068
Compare
storybook-bot
force-pushed
the
version-patch-from-7.6.12
branch
13 times, most recently
from
February 2, 2024 09:22
1a6256a
to
32050d2
Compare
storybook-bot
force-pushed
the
version-patch-from-7.6.12
branch
4 times, most recently
from
February 3, 2024 23:56
f6c52ce
to
56e117f
Compare
github-actions
bot
requested review from
yannbf,
valentinpalkovic and
ndelangen
as code owners
February 3, 2024 23:56
storybook-bot
force-pushed
the
version-patch-from-7.6.12
branch
from
February 5, 2024 12:01
56e117f
to
88990a8
Compare
…tests-v2 React Native: Fix errors on compose story
storybook-bot
force-pushed
the
version-patch-from-7.6.12
branch
from
February 5, 2024 13:59
88990a8
to
9b0a162
Compare
storybook-bot
force-pushed
the
version-patch-from-7.6.12
branch
5 times, most recently
from
February 6, 2024 07:46
9776868
to
71df07f
Compare
storybook-bot
force-pushed
the
version-patch-from-7.6.12
branch
from
February 6, 2024 11:24
71df07f
to
2f353e5
Compare
github-actions
bot
requested review from
kasperpeulen and
JReinhold
as code owners
February 6, 2024 13:48
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
7.6.12
to7.6.13
.Once this pull request is merged, it will trigger a new release of version
7.6.13
.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:🍒 Manual cherry picking needed!
The following pull requests could not be cherry-picked automatically because it resulted in merge conflicts.
For each pull request below, you need to either manually cherry pick it, or discard it by replacing the "patch:yes" label with "patch:no" on the PR and re-generate this PR.
git cherry-pick -m1 -x a91240a3ba7cd784f5fbdea6152c3cf70381e78d
git cherry-pick -m1 -x dda22268517d1c4aba870bd55b557616a8b87463
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
7.6.13