Bump all packages #8237
Merged
Bump all packages #8237
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
🦋 Changeset detectedLatest commit: c17d512 The changes in this PR will be included in the next version bump. This PR includes changesets to release 48 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Size Report 1Affected ProductsNo changes between base commit (506b8a6) and merge commit (7ac9e67).Test Logs |
Size Analysis Report 1Affected ProductsNo changes between base commit (506b8a6) and merge commit (7ac9e67).Test Logs |
DellaBitta
approved these changes
May 9, 2024
dlarocque
approved these changes
May 9, 2024
Merged
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.
Bump all packages by a patch.
Staging release selectively publishes only packages that had their versions bumped, and their direct dependencies (not transitive dependencies), which means on npm installs there are 2 versions of
@firebase/appwhich causes component registration to be very buggy. This will roll into the existing "Version Packages" staging PR, so everything that's bumped minor there will stay minor, and any other package will be bumped by a patch from this changeset.The long term solution is to fix the staging release check to publish all the packages that would need to be published, for this release, I just want to make sure we have a staging release to test with ASAP, and also be 100% sure we don't have a problem in prod.