Update Node.js Engine Inventory

[heroku-linguist]

Automated pull-request to update heroku/nodejs engine inventory:

• Added Node.js version 22.9.0.

[jraoult]

@colincasey I had a situation where my automated dependency updates bot was too fast to upgrade to Node v22.9. My checks passed in CI (GitHub actions), but when deployed to Heroku, the build pack couldn't find the Node version, and our staging environment failed to build. That's what staging is for, but I'd rather avoid auto-merging a node upgrade that could break the build once it is deployed in Heroku.

I could enforce a longer delay before the bot tries to upgrade the Node version (currently set to 3 days). So, what's the typical delay between a Node release and the time the update to the "inventory" is merged and released? Alternatively, is there a way to "pre-check" that a particular app will be successfully built?

[colincasey]

Hi @jraoult, sorry to hear the delay in getting this buildpack released has caused you trouble. I do try my best to publish this buildpack within 1 day of new Node.js releases but, as is the way with most things, sometimes external factors get in the way. Case in point, I won't be able to release the recent changes for this buildpack until Monday (Sept. 23rd).

If this is currently blocking you, what you can do instead of waiting for the official release is (temporarily) replace the heroku/nodejs buildpack in your app's buildpack list with https://github.com/heroku/heroku-buildpack-nodejs#latest which will load the buildpack directly from GitHub.

As for the most reliable way you could "pre-check" if the latest Node.js version would successfully build on Heroku is by using a Review App.

[jraoult]

@colincasey no worries. I just rolled back the automated upgrade.

Heroku is by using a Review App.

We used to have auto Review App creation for every PR. Still, we realised it wasn't blocking the PR auto-merge in some situations because the other checks would finish before the review even added time to start building—sort of a race condition. I need to look at that again and see if there is a way to make it work. In the meantime, I just disabled auto merge for Node upgrade-related PR so I can manually check.