Use future version of satellite repo dependencies #22026
Merged
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.
We have created a new npm tag,
future
to isolate 7.1 changes from users upgrading to 7.0 on either thelatest
ornext
tags. This is a workaround for a circular dependency issue that we have between the monorepo and a few satellite repos. We will attempt to fix this problem properly in a later effort, but in the short term the following satellite repos havefuture
releases which point back to thefuture
tag on the monopo. Thenext
branch on the monorepo will release to thefuture
npm tag for the coming month.