Nathan Rajlich
Nathan Rajlich
I think #36 fixes it…
In my case, this happened when running tests against fixtures that specify different `packageManager` versions. The tests themselves are run through yarn though.
There has already been at least two [[1]](https://github.com/yarnpkg/yarn/issues/9015#issuecomment-1821403144)[[2]](https://github.com/yarnpkg/yarn/issues/9015#issuecomment-1834322421) explanations of situations where this change broke existing setups. I'm not sure why you are confused.
I'm not sure I agree that the scenarios described would be considered invalid setups. They are sub-packages that are not meant to be considered part of the workspace. The yarn...
I am experiencing this as well. Is there any explanation?
Thanks @matthewdowns-eb. That's more of a workaround though. I'm more interested in _why_ it's happening.
Sorry for the delay everyone. We'll be looking to get this merged soon. In the meantime, you can set env var `VERCEL_CLI_VERSION` with value of `https://vercel-git-fork-stefma-go-support.vercel.sh/tarballs/vercel.tgz` to create a deployment...
@hussamkhatib I can not reproduce with that. Can you show the _exact_ steps please?
For anyone who has been bitten by this bug, can I ask you to try installing this version of the CLI and let me know if that fixes it for...
@sanderkranz Yes, this is expected. What is the issue? And just to confirm, are you using `vc link --repo`?