Skip to content

Conversation

Ashesh3
Copy link
Contributor

@Ashesh3 Ashesh3 commented Jun 27, 2021

Since the said issue is resolved and shipped in 16.4, Suggesting users to downgrade is a bad idea, instead they should be recommended to upgrade to the latest release to resolve this issue.

Reference: nodejs/node#38273

Since the said issue is resolved and shipped in 16.4, Suggesting users to downgrade is a bad idea, instead they should be recommended to upgrade to the latest release to resolve this issue.

Reference: nodejs/node#38273
@connor4312
Copy link
Member

connor4312 commented Jun 27, 2021

Excellent, thanks! I think, in the future for these cases, we should say to try upgrading if a newer version is available.

@connor4312 connor4312 merged commit e93c6d6 into microsoft:main Jun 27, 2021
@Ashesh3 Ashesh3 deleted the patch-1 branch June 28, 2021 03:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants