ci(repo): tolerate pnpm warnings in turbo validate step#8624
Conversation
🦋 Changeset detectedLatest commit: 4708a41 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughThis PR improves the robustness of Turbo task validation in the CI workflow. The Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/dev-cli
@clerk/expo
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/hono
@clerk/localizations
@clerk/nextjs
@clerk/nuxt
@clerk/react
@clerk/react-router
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/ui
@clerk/upgrade
@clerk/vue
commit: |
Two integration shards flaked today on a
jq: parse errorbefore any test ran.The culprit was
pnpm turbo run <task> --dry=jsonhavingWARN Unsupported engine: wanted node >=24.15.0 (current v20.20.0)prepended to stdout, which brokejq. That warning shows up whenuseblacksmith/setup-nodedoesn't successfully swap the runner's Node 20 for Node 24, but the deeper issue is that the preflight assumed pnpm's stdout was pure JSON.Drops anything before the first
{so the validate step survives stray pnpm output, independent of which Node version ends up active on the runner.