Adrien
Adrien
Indeed I could find the example by searching the repo. yep will do within this week 👍
👋 I think it does not completely solve the issue. The build is ok BUT the deploy now fails silently with `RangeError: Invalid array length`. Do you confirm the same...
Although it seems that moving to npm will introduce another issue of access right during the build: https://github.com/netlify/cli/issues/1870 do you reproduce on your CI too?
For instance I tried that branch which implements the fix `uses: mannum/netlify-actions/cli@master` and face the issue https://github.com/mannum/netlify-actions/blob/master/cli/Dockerfile#L12 I am running on `runs-on: ubuntu-latest`
> Oops. I was experiencing the same problem 😵💫 I'm sorry I didn't notice. I think you are still using yarn, but the package has been somehow "removed" to not...
It would be nice if the Netlify team could maintain this and put that into their OKRs, especially for paid customer. #rant
I found it, that requires to upgrade the node version of the image to the most recent if we want to use npm: https://github.com/netlify/cli/issues/1870#issuecomment-799845077 Their version is still node 12...
I don't know why with Yarn it keeps failing but using npm you need a recent version of node/npm. Works on my end with ```dockerfile FROM node:16-alpine LABEL version="1.0.1" LABEL...
May be some cache on yarn? idk
I would vote for `instanceRef`, as it is very similar to what CloudFormation would do for instance.