fix: resolve pnpm conflict and update supabase-js to v2.117.2 - #539
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
These were committed by mistake when pnpm ran at the repo root; the root package.json exists only for corepack's packageManager pin and has no workspace of its own. Ignoring node_modules/ at the root prevents this from recurring, and it broke the check-prettier job's node_modules cleanup step (it tried to auto-commit the deletion and push to a detached HEAD). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
imor
approved these changes
Sep 28, 2026
This branch was successfully deployed
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
2 participants
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.
Fixes the
update-supabase-jsworkflow, which failed because the Setup pnpm step hardcodedversion: 9while the repo pins pnpm via thepackageManagerfield, causingpnpm/action-setupto error on the conflicting versions. The step now reads the version fromwebsite/package.jsoninstead, matching the pattern already used inwebsite-tests.yaml.Also bumps
@supabase/supabase-jsfrom 2.107.0 to 2.117.2.