BREAKING CHANGE: upgrade to Lit 3 #211
Merged
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
dbatiste
approved these changes
May 3, 2024
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
🎉 This PR is included in version 6.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
👋 Hey, we're upgrading to Lit 3! 🎉 This PR prepares this repo for the upgrade, which will happen starting May 21st. Someone from team Gaudí will take care of everything (except approving this PR), so sit back and enjoy the upgrade!
A Phased Approach
Merges will happen in several phases based on where each repo sits in the overall dependency graph of Lit-related things.
This repo will be in phase: 3 of 10
Since this repo is in a downstream phase, its dependency versions that use Lit 3 haven't released yet, so its CI will be in a broken state. This will be resolved when the previous phase of upgrades completes.
Next steps
CODEOWNERSapprovals received 👍 (you can do that now to avoid holding up the upgrade later!)main/masterto pick up latest changesIf this repo has apackage-lock.json, update to latest dependencies