Avoid failure if @types/node is already 12.12#1008
Merged
edoardopirovano merged 1 commit intomainfrom Mar 30, 2022
Merged
Conversation
henrymercer
approved these changes
Mar 30, 2022
cadc4ec to
a9095ce
Compare
This was referenced Apr 25, 2023
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
2 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.
Cherry-picks 9da34a6, which we already have on the
v1branch (where it is needed to avoid a failure) ontomain. I think we should do this so that our PR checks are the same on all the branches, even though we don't need it outside ofv1.Merge / deployment checklist