[Node.js] On scalingo-18 this buildpack resolves Node.js to an incompatible version

[johnsudaar]

Node 18 broke the compatibility with Ubuntu 18.04 (used by our scalingo-18 stack) see: nodejs/node#42351

Currently any build done on scalingo-18 that needs Node.JS without freezing it to a version <= 17 are failing with the following error:

node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by node)

Related to SRE-443

[EtienneM]

I can see the PHP buildpack uses a Semver server located at semver.io.

https://github.com/Scalingo/php-buildpack/blob/91b9bcb0ac487be86539826147a2621387ccf5fd/lib/nodejs#L39

Maybe part of the solution to this problem is to use our own Semver app (https://semver.scalingo.com/) so that we can control what it returns by default?

Or maybe the solution is to write a nice message in case we detect Node.js >= 18 and the stack scalingo-18 so that we display a nice error message?

[johnsudaar]

It could be a good solution. Switch to https://semver.scalingo.io/node-$STACK/resolve/$SEMVER_RANGE and ensure that it resolved correctly (currently it doesn't).

I'm not found of the message. IMHO if the user doesn't specify any Node.JS version, we should resolve it correctly.

IMHO the fix is in 2 parts:

1. use our semver (with the stacks)
2. Fix our semver so that it doesn't resolve Node 18 on scalingo-18 stacks.

[brandon-welsch]

Another customer impacted: https://app.intercom.com/a/apps/w4oogu7s/inbox/inbox/all/conversations/12375700070668

[EtienneM]

The path https://semver.scalingo.com/node-scalingo-18/versions shouldn't resolve versions > 16

[ipfaze]

Closing this issue as our stack scalingo-18 is deprecated and all customer's application are at least on scalingo-20.