feat(storage): ✨ update Supabase Storage adapter to use secretKey instead of serviceRoleKey

[aXenDeveloper]

Improving Documentation

• Run pnpm lint:fix to fix formatting issues before opening the PR.
• Read the Docs Contribution Guide: https://vitnode.com/docs/dev/contribution

Description

What?

Why?

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
vitnode-docs	Canceled		Jul 8, 2026 6:27pm

[gemini-code-assist]

Code Review

This pull request migrates the Supabase Storage adapter configuration from using the legacy serviceRoleKey to the new secretKey (SUPABASE_SECRET_KEY), updating the documentation, environment examples, and adapter implementation accordingly. It also adds vitest testing scripts and dependencies to the s3 and supabase-storage packages. The review feedback highlights that completely removing serviceRoleKey from the adapter signature is a breaking change. It is recommended to keep serviceRoleKey as a deprecated fallback in both the adapter implementation and the API configuration to maintain backward compatibility with existing deployments.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.