I am writing to express my disappointment with the recent release of version 1.6.0 of the Grunt package. While I understand the desire to update the package with new features and improvements, this particular release includes breaking changes that have caused significant disruption to my workflow.
According to normal practices, users typically update to the latest minor version changes which do not include breaking changes. However, with the release of version 1.6.0, users are required to update their Node.js version to 16+. If someone uses "grunt": "^1.5.3" in their package.json file and does not use a .lock file for package installation, it will automatically install version 1.6.0 of Grunt and result in errors on machines where the Node version is not >=16.
This goes against best practices in the Software Development Life Cycle (SDLC) and creates unnecessary challenges for users. I would strongly recommend that, in the future, major releases like this one be labeled as version 2.0.0 so that users can plan to update to the new version without encountering breaking changes in their production environments.
I hope that you take my concerns into consideration as you continue to develop and release new versions of Grunt. I look forward to hearing back from you on this matter.
Dear Grunt Team,
I am writing to express my disappointment with the recent release of version 1.6.0 of the Grunt package. While I understand the desire to update the package with new features and improvements, this particular release includes breaking changes that have caused significant disruption to my workflow.
According to normal practices, users typically update to the latest minor version changes which do not include breaking changes. However, with the release of version 1.6.0, users are required to update their Node.js version to 16+. If someone uses "grunt": "^1.5.3" in their package.json file and does not use a .lock file for package installation, it will automatically install version 1.6.0 of Grunt and result in errors on machines where the Node version is not >=16.
This goes against best practices in the Software Development Life Cycle (SDLC) and creates unnecessary challenges for users. I would strongly recommend that, in the future, major releases like this one be labeled as version 2.0.0 so that users can plan to update to the new version without encountering breaking changes in their production environments.
I hope that you take my concerns into consideration as you continue to develop and release new versions of Grunt. I look forward to hearing back from you on this matter.