So I successfully managed to force an update of node on the server by running node -v > .nvmrc, however doing so caused an issue with sharp module for some reason.
Currently still trying to debug that and find out exactly why, error is:
The module '/opt/build/repo/node_modules/sharp/build/Release/sharp.node' was compiled against a different Node.js version using NODE_MODULE_VERSION 57. This version of Node.js requires NODE_MODULE_VERSION 64. Please try re-compiling or re-installing
Well, yes. You’ve changed node version, and sharp is very node version dependent. You’d have to clear the cache one more time (on each branch) to prevent that clash. If you still get it with a cleared cache, seems sharp is somehow getting built using different node by your build pipeline - if you see that, is it a normal dependency in your yarn.lock?