Bumped version to 16.4.3-alpha.0 #13448
Merged
Conversation
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
Contributor
Author
|
I test this by syncing to this PR |
mihalskiy
approved these changes
Aug 20, 2018
gaearon
approved these changes
Aug 20, 2018
Collaborator
gaearon
left a comment
gaearon
left a comment
There was a problem hiding this comment.
Looks good. CI error is weird?
Contributor
Author
|
Yeah... I'm not sure what's going on with that CI error. |
Contributor
Author
|
CI is backed up b'c Circle's having problems, but I ran the same commands locally and the above change should fix this issue so.... |
NMinhNguyen
referenced
this pull request
in enzymejs/react-shallow-renderer
Jan 29, 2020
* Bumped version to 16.4.3-alpha.0 * Bump react-is peer dep version in react-test-renderer
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
In order to make the changes in this PR work, which in turn unblocks a React FB sync, we need to bump the Raect version. Turns out, the version bump was never committed after the recent 16.4.2 release– so this PR jumps it straight to 16.4.3-alpha.0.
This is a little weird, since we don't typically bump until release time. I'm open to other suggestions if anyone else has a better idea.