[create-cloudflare] Pass pnpm settings through Turbo - #15067
Conversation
|
|
Codeowners approval required for this PR:
Show detailed file reviewers |
3c3792a to
2f32ae2
Compare
@cloudflare/autoconfig
@cloudflare/build-output-utils
@cloudflare/config
create-cloudflare
@cloudflare/deploy-helpers
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-functions
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-auth
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
|
This appears to break a lot of C3 CI... |
2f32ae2 to
8d4a1e4
Compare
|
I believe the PR description is not accurate. At least in CI I think we run turbo in strict mode, hence the need to add these? |
workers-devprod
left a comment
There was a problem hiding this comment.
Codeowners reviews satisfied
|
@petebacondarwin We do You can see the VP PR logged this too: https://github.com/cloudflare/workers-sdk/actions/runs/31407924446/job/93518674222#step:5:104 |
|
To clarify: We run CI in strict mode only on forks PR as the setup I mentioned above will run only if |
Pass the pnpm 11
pmOnFailandverifyDepsBeforeRunsettings through Turbo for C3 E2E tests.Fork PRs run Turbo in strict mode because they do not receive remote-cache secrets, so these workflow settings were being dropped. Version Packages runs in loose mode, which is why it passed. Declaring the settings in
turbo.jsonmakes both trusted and fork runs use the intended pnpm version while retaining pnpm 10 compatibility.This blocks #14924 from being merged 😅
A picture of a cute animal (not mandatory, but encouraged)