-
Notifications
You must be signed in to change notification settings - Fork 2k
turbo-ignore
is incompatible with pnpm catalogs
#10048
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I can see that prune in 2.4.3 and 2.4.4 is also not working together with pnpm catalogs. should that be different issue? |
Yes, please open a separate issue with a reproduction repository if possible. |
cprussin
added a commit
to pyth-network/pyth-crosschain
that referenced
this issue
Mar 16, 2025
This breaks `turbo-ignore`'s ability to detect the turbo version and results in Vercel being unable to skip unneeded builds. See vercel/turborepo#10048
3 tasks
3 tasks
chris-olszewski
added a commit
that referenced
this issue
May 8, 2025
### Description Fixes #10048 Do not attempt to use `catalog` protocol to fetch the specified version of `turbo`. Instead warn and fall back to inferring from `turbo.json`. ### Testing Instructions Added unit tests for this case
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Verify canary release
Link to code that reproduces this issue
https://github.com/dBianchii/turbo-ignore-pnpm-catalog-issue
Which canary version will you have in your reproduction?
2.4.3-canary.4
Enviroment information
Expected behavior
It should not error when I run
pnpx turbo-ignore
,npx turbo-ignore
, or pnpm turbo-ignore` while having a catalog: setting for my turbo package in my turborepo repository.Actual behavior
When I run turbo-ignore from any package, I get this:
To Reproduce
Clone repo, install deps with
pnpm i
, then run eitherpnpx turbo-ignore
ornpx turbo-ignore
.Additional context
No response
The text was updated successfully, but these errors were encountered: