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
Grunt 1.6.0 removes support for NodeJS v14, which is reasonable considering its age (could this have waited until April when it goes End of Life, though?).
However, removal of support for a specific NodeJS version is considered by some to be a breaking change, and therefore requires a major version bump (Grunt 2.0.0 rather than 1.6.0).
Would you consider updating your policies and procedures for next time a NodeJS version is retired (September 11th, 2023 for NodeJS v16: https://nodejs.org/en/blog/announcements/nodejs16-eol/) so that a major version bump is performed?
The text was updated successfully, but these errors were encountered:
Would you consider updating your policies and procedures for next time a NodeJS version is retired (September 11th, 2023 for NodeJS v16: https://nodejs.org/en/blog/announcements/nodejs16-eol/) so that a major version bump is performed?
Yeap I think that's fair 👍 Historically we haven't been bumping major releases like this.
Grunt 1.6.0 removes support for NodeJS v14, which is reasonable considering its age (could this have waited until April when it goes End of Life, though?).
However, removal of support for a specific NodeJS version is considered by some to be a breaking change, and therefore requires a major version bump (Grunt 2.0.0 rather than 1.6.0).
Would you consider updating your policies and procedures for next time a NodeJS version is retired (September 11th, 2023 for NodeJS v16: https://nodejs.org/en/blog/announcements/nodejs16-eol/) so that a major version bump is performed?
The text was updated successfully, but these errors were encountered: