The change looks good but would it be possible to exclude the Yarn and signature key changes from the PR?

Sure. I ran ./update.sh and thought that's ok.
Ready to go.

FWIW, I don't think it should be up to the docker image to tell npm not to "misbehave". Then again, this isn't a huge burden for us, so 🤷

/cc @nodejs/npm thoughts?

Checked with the team and it does sounds like the default should be sh instead, we'll fix it soon 😊 thanks for the heads up @SimenB

@ruyadorno thanks! Please let us know when it's fixed, so we can close this issue ;)

@PeterDaveHello the fix went out in the npm@7.0.7 release which has already been merged to node master and is going out in the node@15.1.0 release: nodejs/node#35948 let me know once that's out if all related issues are solved 😊

Sure, thanks @ruyadorno

Closing as the 15.1.0 images have been pushed to the docker hub

For reference: npm/cli#2067