You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains 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
The reason will be displayed to describe this comment to others. Learn more.
Quite the breaking change this is..! Our build pipeline just failed because of it. Definitely should be a major bump.
Also: The "node 14 no longer supported" message to me reads as if just node 14 is no longer supported, not that node 16 is no longer supported either.
8a69def
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Breaking change, no? Convention has become "do a major bump when you drop support for an older node version".
8a69def
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Quite the breaking change this is..! Our build pipeline just failed because of it. Definitely should be a major bump.
Also: The "node 14 no longer supported" message to me reads as if just node 14 is no longer supported, not that node 16 is no longer supported either.
8a69def
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://nodejs.org/en/blog/announcements/nodejs16-eol/
It's been EOL for 10 months now. Pin your deps.