chore: bump node min version to 10.13.0 #22400
We have a project that depends on on Gatsby version
Should have this bump been in a major version (3.0.0) for gatsby-cli? If so it would be helpful if you could publish some new versions to address it.
I will look into the possibility of having a locked version by modifying a package-lock, and of course upgrading the project. This project is something that we're maintaining without active feature development so you can imagine this is not trivial.
Just raising in case this is helpful, I may be mistaken, let me know if you'd like any more information.
@NickColley Thanks for the heads up!
We are very sorry for this situation, we are always trying to not do changes like that during minor releases. Unfortunately we didn't have a proper major version release process, which forced us to do this kind of change because of Node deprecation. We are changing the process so that we have a regular major version release cadence and this will let us be more stable in between those releases.
I recommend locking the version in package-lock.json for now or upgrading Node - there shouldn't be any breaking changes except for node version between those versions of Gatsby.
It would be really helpful if you could commit to your stance here:
In the meantime I'll attempt to upgrade our applications dependencies as pinning the version in the package-lock is not working out. Thanks for the reply, good luck.