I’m seeing this error. What’s strange is, I use the same circleci script for another project, using all the same versions in the package.json (the repos backing the projects are configured identically), and it works fine. I’ve tried removing the lines that restore caches, doing the dependencies force thing I found elsewhere, nothing seems to work, the yarn install just dies there.
This is really sort of in my way, I can’t get full pipeline deploy out, I have to do a manual build/sync.
It looks like it is requesting information on a specific package. I wonder, maybe 3.3.6 is an unsupported version? If so, is there a yarn update to help it get the latest versions in its remote repo?
Ah, I just did this search and found this report - it says that this version has been unpublished.
Think I fixed it (figures, I’m stuck for a day, post the question, and 15 minutes later figure it out). Posting as it may help somebody else out.
Here’s what I did:
Delete yarn.lock file, push the repo without it. The CI will say couldn’t find the file, continue to run, etc. Problem seemed to go away other than the failure on not finding yarn.lock.
Reinstalled repo with yarn (creates new lock file). Pushed, CI dependency error went away.
Make sure it still passes your tests. A better fix might have been to amend the one library to the first release after the unpublished version, and then update.