CyrilChandelier
Github personal access token stopped working using yarn/npm install
I have a NodeJS project that uses yarn to resolve dependencies. One notable feature of my config is that one of the package is a private repo and the resolve downloads the package using a Github Personal Access Token, something like:
This was working last Friday, but it stopped working today. I'm now seeing yarn error code 128 in the deploy logs with not much more information.
The
yarn install works locally, but fails on Railway.
I tried to migrate to npm instead of yarn, same error. Same here, the npm install works locally, but fails on Railway.
I verified the validity of my personal access token, it's valid. I even generated a new one to try but that didn't work either.
I tried to redeploy the last build that passed on Friday, it now fails, so something definitely changed in between this last build and now.
I'm running out of ideas, I would appreciate some help. Thanks.19 replies