Skip to content

[Snyk] Upgrade @supabase/supabase-js from 2.76.1 to 2.86.2#70

Open
ssdeanx wants to merge 1 commit intomainfrom
snyk-upgrade-67638d5eb8f4f09c51b687b06f3890d3
Open

[Snyk] Upgrade @supabase/supabase-js from 2.76.1 to 2.86.2#70
ssdeanx wants to merge 1 commit intomainfrom
snyk-upgrade-67638d5eb8f4f09c51b687b06f3890d3

Conversation

@ssdeanx
Copy link
Copy Markdown
Owner

@ssdeanx ssdeanx commented Dec 27, 2025

snyk-top-banner

Snyk has created this PR to upgrade @supabase/supabase-js from 2.76.1 to 2.86.2.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 45 versions ahead of your current version.

  • The recommended version was released 23 days ago.

Release notes
Package name: @supabase/supabase-js
  • 2.86.2 - 2025-12-04

    2.86.2 (2025-12-04)

    🩹 Fixes

    • storage: correct QueryVectorsResponse to use vectors instead of matches (#1922)

    ❤️ Thank You

  • 2.86.2-canary.0 - 2025-12-04

    2.86.2-canary.0 (2025-12-04)

    🩹 Fixes

    • storage: correct QueryVectorsResponse to use vectors instead of matches (#1922)

    ❤️ Thank You

  • 2.86.1 - 2025-12-04

    2.86.1 (2025-12-04)

    🩹 Fixes

    • auth: suppress getsession warning when getuser is called first (#1898)
    • auth: code verifier remains in storage during edge cases (#1759)
    • postgrest: cross-schema rpc setof type inference (#1900)
    • repo: update lock file (#1910)
    • repo: lock file issues (#1919)
    • repo: update npm and install again (#1920)
    • supabase: add esm wrapper to resolve module not found error in nuxt (#1914)

    ❤️ Thank You

  • 2.86.1-canary.0 - 2025-12-04

    2.86.1-canary.0 (2025-12-04)

    🩹 Fixes

    • auth: suppress getsession warning when getuser is called first (#1898)
    • auth: code verifier remains in storage during edge cases (#1759)
    • postgrest: cross-schema rpc setof type inference (#1900)
    • repo: update lock file (#1910)
    • repo: lock file issues (#1919)
    • repo: update npm and install again (#1920)
    • supabase: add esm wrapper to resolve module not found error in nuxt (#1914)

    ❤️ Thank You

  • 2.86.0 - 2025-11-26

    2.86.0 (2025-11-26)

    🚀 Features

    • storage: install iceberg-js and add from method (#1881)

    ❤️ Thank You

  • 2.85.1-canary.0 - 2025-11-26

    2.85.1-canary.0 (2025-11-26)

    🚀 Features

    • storage: install iceberg-js and add from method (#1881)

    ❤️ Thank You

  • 2.85.0 - 2025-11-26

    2.85.0 (2025-11-26)

    🚀 Features

    • realtime: add metadata to realtime user broadcast push (#1894)

    🩹 Fixes

    • auth: oauth minor fixes on types (#1891)

    ❤️ Thank You

  • 2.84.1-canary.1 - 2025-11-26

    2.84.1-canary.1 (2025-11-26)

    🚀 Features

    • realtime: add metadata to realtime user broadcast push (#1894)

    ❤️ Thank You

    • Eduardo Gurgel
  • 2.84.1-canary.0 - 2025-11-26

    2.84.1-canary.0 (2025-11-26)

    🩹 Fixes

    • auth: oauth minor fixes on types (#1891)

    ❤️ Thank You

  • 2.84.0 - 2025-11-20

    2.84.0 (2025-11-20)

    🚀 Features

    • postgrest: add isdistinct and regex pattern matching operators (#1875)

    🩹 Fixes

    • postgrest: validate empty or invalid relation names in Postgrest… (#1863)
    • realtime: simplify serializer by removing unnecessary types of messages (#1871)

    ❤️ Thank You

  • 2.83.1-canary.2 - 2025-11-19
  • 2.83.1-canary.1 - 2025-11-19
  • 2.83.1-canary.0 - 2025-11-19
  • 2.83.0 - 2025-11-18
  • 2.82.1-canary.0 - 2025-11-18
  • 2.82.0 - 2025-11-18
  • 2.81.2-canary.3 - 2025-11-18
  • 2.81.2-canary.2 - 2025-11-18
  • 2.81.2-canary.1 - 2025-11-17
  • 2.81.2-canary.0 - 2025-11-12
  • 2.81.1 - 2025-11-11
  • 2.81.1-canary.1 - 2025-11-11
  • 2.81.1-canary.0 - 2025-11-11
  • 2.81.0 - 2025-11-10
  • 2.80.1-canary.5 - 2025-11-10
  • 2.80.1-canary.4 - 2025-11-07
  • 2.80.1-canary.3 - 2025-11-07
  • 2.80.1-canary.2 - 2025-11-07
  • 2.80.1-canary.1 - 2025-10-01
  • 2.80.1-canary.0 - 2025-10-01
  • 2.80.0 - 2025-11-06
  • 2.79.1-canary.2 - 2025-10-03
  • 2.79.1-canary.1 - 2025-10-02
  • 2.79.1-canary.0 - 2025-10-02
  • 2.79.0 - 2025-11-04
  • 2.78.1-canary.1 - 2025-11-04
  • 2.78.1-canary.0 - 2025-10-31
  • 2.78.0 - 2025-10-30
  • 2.77.1-canary.2 - 2025-10-30
  • 2.77.1-canary.1 - 2025-10-30
  • 2.77.1-canary.0 - 2025-10-29
  • 2.77.0 - 2025-10-29
  • 2.76.2-canary.2 - 2025-10-23
  • 2.76.2-canary.1 - 2025-10-22
  • 2.76.2-canary.0 - 2025-10-21
  • 2.76.1 - 2025-10-21
from @supabase/supabase-js GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade @supabase/supabase-js from 2.76.1 to 2.86.2.

See this package in npm:
@supabase/supabase-js

See this project in Snyk:
https://app.snyk.io/org/ssdeanx/project/97f9b44f-04aa-4c4a-a071-4c3e5cc49f97?utm_source=github&utm_medium=referral&page=upgrade-pr
Copilot AI review requested due to automatic review settings December 27, 2025 09:15
@continue
Copy link
Copy Markdown

continue Bot commented Dec 27, 2025

All Green - Keep your PRs mergeable

Learn more

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts


Unsubscribe from All Green comments

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Dec 27, 2025

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch snyk-upgrade-67638d5eb8f4f09c51b687b06f3890d3

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Copy Markdown

🤖 Hi @ssdeanx, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @ssdeanx, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the @supabase/supabase-js client library to its latest stable version. The primary goal is to ensure the project benefits from the most recent bug fixes, performance improvements, and new features provided by the Supabase team, thereby improving the application's stability and leveraging modern capabilities.

Highlights

  • Dependency Upgrade: The @supabase/supabase-js dependency has been upgraded from version 2.76.1 to 2.86.2.
  • Automated Update: This pull request was automatically generated by Snyk to keep the dependency up-to-date, enhancing security and maintainability.
  • Included Changes: The upgrade incorporates 45 versions of changes, including various bug fixes across authentication, storage, and Postgrest modules, as well as new features like adding metadata to realtime broadcasts and new Postgrest operators.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@github-actions
Copy link
Copy Markdown

🤖 I'm sorry @ssdeanx, but I was unable to process your request. Please see the logs for more details.

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR upgrades the @supabase/supabase-js package from version 2.76.1 to 2.86.2, spanning 45 versions released over approximately 2 months. The upgrade includes bug fixes for authentication, storage improvements with vector query support, and realtime enhancements.

Key changes:

  • Updates @supabase/supabase-js to version 2.86.2 with auth, storage, and realtime improvements
  • Removes deprecated @supabase/node-fetch dependency (now handled internally)
  • Adds new iceberg-js dependency for enhanced storage capabilities

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File Description
package.json Updates @supabase/supabase-js dependency version from ^2.76.1 to ^2.86.2
package-lock.json Reflects dependency tree changes including removal of @supabase/node-fetch, addition of iceberg-js, and updates to all @supabase/* sub-packages with Node >= 20.0.0 requirement

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request from Snyk upgrades @supabase/supabase-js from version 2.76.1 to 2.86.2. This is a significant jump across 45 versions. While it's a minor version update and should be backward-compatible, the large scope of the upgrade introduces a risk of subtle regressions, particularly in authentication flows where this library is heavily used. I have added a comment to the package.json file highlighting this risk and recommending careful validation.

Comment thread package.json
"@radix-ui/react-tabs": "^1.1.13",
"@supabase/ssr": "^0.7.0",
"@supabase/supabase-js": "^2.76.1",
"@supabase/supabase-js": "^2.86.2",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This dependency upgrade for @supabase/supabase-js jumps 45 minor versions. While semantic versioning suggests these updates should be backward-compatible, such a large leap introduces a non-trivial risk of subtle regressions or behavioral changes that could impact your application. Given this library's critical role in authentication, a safer approach could be to upgrade incrementally through smaller version steps to isolate any potential issues. If you proceed with this large jump, extensive regression testing of all authentication flows is highly recommended to ensure stability.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants