We’ve done nothing special to change this behaviour. There’s no reason for Netlify to trigger a change that would specifically affect a minor x.x.1 update in Node.js and break so many builds.
I’ve always used the NODE_VERSION as node in my Site Settings. So I have been using version 16.5.1+ much before it went into the “latest LTS” stage a few days ago and I’m having this issue since then.
To be clear, we’re not doing anything special with building packages or installing Node Modules. We’re simply calling npm install:
github.com//dl.bintray.com/sbt/debian /" | tee -a /etc/apt/sources.list.d/sbt.list \&& apt-get update \
&& apt-get install -y --force-yes sbt \
&& sbt --version
At the end, I print the sbt version.
If I let this last line my docker build fail with the following error :
INFO[0061] The command [/bin/sh -c echo "deb //dl.bintray.com/sbt/debian /" | tee -a /etc/apt/sources.list.d/sbt.list && apt-get update && apt-get install -y --force-yes sbt && sbt --version] returned a non-zero code: 1
If i remove this last line, my docker build is OK.
Why do "sbt --version" return a non-zero code ??
Jules