Supabase
Replies: 2 comments 2 replies
|
This makes sense and aligns with standard runtime support expectations across the ecosystem. Once a Node.js release reaches EOL, continuing to officially support it becomes increasingly risky — especially for libraries handling authentication, realtime connections, storage operations, database access, and server-side function execution. Security patches, OpenSSL updates, dependency compatibility, and runtime behavior all become harder to guarantee on unsupported versions. Appreciate the early notice and the clear migration timeline. Giving developers until June 30, 2026 provides a reasonable upgrade window for teams managing production deployments, CI pipelines, Docker images, serverless runtimes, and monorepos with pinned Node versions. For teams preparing the migration, it may also help to highlight a few operational considerations:
It could also be useful to publish:
Related references:
Overall, this seems like a reasonable and responsible move from a long-term maintenance and security perspective. |
|
Related PR: supabase/supabase-js#2482 |
|
What about the Deno version? |
|
Hi @sebprx, thanks for asking! This deprecation notice only concerns Node.js 20. Deno support follows its own, separate policy and is not affected by this change at all. As documented in the Support Policy (https://github.com/supabase/supabase-js?tab=readme-ov-file#support-policy), we support Deno versions from the stable and lts release channels, following Deno's own release schedule. Dropping Node.js 20 does not change anything about which Deno versions are supported, and no Deno version is being dropped as part of this. If a Deno version does reach end of life in the future, we will post a separate deprecation notice for that, the same way we did for Node.js 18 and now Node.js 20. Hope that clears it up, let me know if you have any other questions! |
Uh oh!
There was an error while loading. Please reload this page.
As part of our ongoing commitment to providing a secure and reliable experience for all developers, we will drop support for Node.js 20 in accordance with our Support Policy.
Affected libraries
All packages published from the supabase-js monorepo:
@supabase/supabase-js
@supabase/auth-js
@supabase/realtime-js
@supabase/functions-js
@supabase/storage-js
@supabase/postgrest-js
Timeline
End of Support for Node.js 20: June 30, 2026
Why?
Node.js 20 reached its official end of life on April 30, 2026 (as scheduled in the Node.js release plan) and no longer receives security updates or critical fixes. Continuing to support unsupported runtimes introduces risks for both developers and end users.
What You Need to Do
Please upgrade to a supported Node.js version (22 or later) before June 30, 2026 to ensure continued compatibility with future releases of our libraries.
Thank you for your attention and continued support. If you have any questions, feel free to reach out through GitHub Discussions or our community channels.
All reactions