CI: run seed-help on Node 22 (native WebSocket)#170
Merged
Conversation
@supabase/supabase-js requires a global WebSocket at client creation, which Node 20 lacks. Node 22 provides it natively. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Load Test Results
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@supabase/supabase-jsneeds a globalWebSocketat client creation, which Node 20 lacks. Bumps the seed job to Node 22. Verified via branch dispatch: the client now connects and processes all 53 rows (remaining failure is an invalidSUPABASE_SERVICE_ROLE_KEYsecret, which is a credential to fix separately).Follow-up to #168/#169.
🤖 Generated with Claude Code