Port 20.0.2 to main #1132
Merged
Port 20.0.2 to main #1132
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
* Update E2E tests to references pending stable JS releases * Update e2e.yml bump component versions to the latest 20.0.0 lineup * Update e2e.yml fixed yaml typo --------- Co-authored-by: George Kudrayvtsev <[email protected]>
Shaptic
approved these changes
Dec 14, 2023
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
port the changes from 20.0.2 back to main
Why
the hotfix is deployed, the ver bump pr, #1125 with
release/v20.0.2became stale, main has moved on, rather than porting newer main back into release/v20.0.2 which alters what delta it represents, using a new branch offrelease/v20.0.2with latest main merged in instead to carry the changes into main.