Deployment using branch fails calling npx comman

Site: magenta-crostata-809f04

When deploying a branch from github named SW-228-feedback-error-page we’re seeing an error (full details at bottom of this post)

It seems that the build process is incorrectly parsing the npx command as it states it’s using
“setup-frontend@latest”

However, we’re not calling setup-frontend@latest

This is the actual command:
npx --yes "leadent-config-manager@latest" setup-frontend -c "some-customer" -e "staging" -i "production" && npm run build

However, when deploying the main branch, this works correctly.

Full error from build log:

npx --yes “leadent-config-manager@latest” setup-frontend -c “some-customer” -e “staging” -i “production” && npm run build
10:41:54 AM: npm ERR! code E404
10:41:54 AM: npm ERR! 404 Not Found - GET https://registry.npmjs.org/setup-frontend - Not found
10:41:54 AM: npm ERR! 404
10:41:54 AM: npm ERR! 404 ‘setup-frontend@latest’ is not in the npm registry.
10:41:54 AM: npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
10:41:54 AM: npm ERR! 404
10:41:54 AM: npm ERR! 404 Note that you can also install from a
10:41:54 AM: npm ERR! 404 tarball, folder, http url, or git url.
10:41:54 AM: npm ERR! A complete log of this run can be found in:
10:41:54 AM: npm ERR! /opt/buildhome/.npm/_logs/2023-06-13T09_41_54_526Z-debug.log
10:41:54 AM: Install for [ ‘setup-frontend@latest’ ] failed with code 1`

Turns out an upgrade from node 14 to 16 (in .nvmrc) fixed this