I have gotten the “upgrade from node 18 to node 22” email a couple of times for one of my projects.
My node version has been set to 22.x for a while now, and has been redeployed since. Why am I getting this message?
Also, the email says the node version is specified on the “General” page of the project’s settings. It is not. It’s on the “Build and Deployment” page.
It’s not a big deal, but what was confusing is that it singled out just one of my repositories, “minerals,” which was not using Node 18 for quite some time.
The reason why you received this notification is because your latest production deployment was still built using Node 18, even though your Node project setting was since updated. Now that you’ve redeployed your project, you shouldn’t get any more deprecation notices. You’re all set!
Also, the email says the node version is specified on the “General” page of the project’s settings. It is not. It’s on the “Build and Deployment” page.
Thanks for pointing this out! We’ll correct it in future emails.