chore: update to recommend 2.16.0 rather than edge channel#699
Merged
chore: update to recommend 2.16.0 rather than edge channel#699
Conversation
|
We are running into problems trying to update to 2.16.0 with bridge. Might be wise to make sure this works flawlessly before recommending this as the default. |
|
Here bridge + 2.16.0 works fine. |
Merged
This file contains hidden or 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
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.
❓ Type of change
📚 Description
With the release of 2.16.0, we can move our recommendation for bridge to consume the normal (but latest) 2.x release, with the expectation that any patches we need for bridge can be released in the usual way.
📝 Checklist