SU

supabase-upgrade-migration

Safely upgrade Supabase SDKs and migrate code using automated scanners and change detection.

Install

mkdir -p .claude/skills/supabase-upgrade-migration && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5403" && unzip -o skill.zip -d .claude/skills/supabase-upgrade-migration && rm skill.zip

Installs to .claude/skills/supabase-upgrade-migration

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Upgrade Supabase SDK and CLI versions with breaking-change detection\
69 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Audit current Supabase SDK and CLI versions
  • Scan codebase for Supabase import sites
  • Identify breaking changes between supabase-js v1 and v2
  • Upgrade @supabase/supabase-js and @supabase/ssr packages
  • Upgrade Supabase CLI and Python SDK
  • Apply code migrations for auth, error handling, and Realtime APIs

How it works

The skill audits current versions, identifies breaking changes, upgrades packages, and applies code transformations for new APIs.

Inputs & outputs

You give it
Supabase project with older SDK/CLI versions
You get back
Supabase project with upgraded SDK/CLI versions and migrated code

When to use supabase-upgrade-migration

  • Upgrading supabase-js SDK
  • Updating Supabase CLI
  • Migrating to v2 APIs
  • Scanning for deprecations

About this skill

Supabase Upgrade Migration

Overview

Upgrade @supabase/supabase-js and the Supabase CLI with breaking-change detection, automated code migration, and rollback planning. Covers the v1-to-v2 migration path (auth method renames, data/error destructuring, realtime API overhaul), minor version bumps, @supabase/ssr adoption, and Python SDK upgrades via pip install --upgrade supabase.

Current State

!npm list @supabase/supabase-js 2>/dev/null | grep supabase || echo 'supabase-js not installed' !supabase --version 2>/dev/null || echo 'CLI not installed' !pip show supabase 2>/dev/null | grep Version || echo 'Python SDK not installed'

Prerequisites

  • @supabase/supabase-js or the Python supabase package installed in the project
  • Git with a clean working tree (no uncommitted changes)
  • Test suite available for post-upgrade verification
  • Node.js >= 18 (for supabase-js v2) or Python >= 3.8 (for Python SDK)

Instructions

Step 1: Audit Versions, Scan Usage, and Review Breaking Changes

Check every installed Supabase package and find all import sites in the codebase.

# Check current SDK version
npm list @supabase/supabase-js

# Check CLI version
supabase --version

# Check Python SDK version
pip show supabase | grep Version

# Find all JS/TS Supabase imports
grep -rn "from '@supabase/supabase-js'" --include="*.ts" --include="*.tsx" --include="*.js" src/ lib/ app/ 2>/dev/null
grep -rn "createClient" --include="*.ts" --include="*.tsx" --include="*.js" src/ lib/ app/ 2>/dev/null

# Find all Python Supabase imports
grep -rn "from supabase" --include="*.py" src/ app/ 2>/dev/null

supabase-js v1 → v2 breaking changes:

v1 Patternv2 ReplacementNotes
createClient(url, key)createClient(url, key)Signature unchanged, but return type differs
supabase.auth.session()supabase.auth.getSession()Sync → async, returns { data: { session } }
supabase.auth.user()supabase.auth.getUser()Sync → async, returns { data: { user } }
supabase.auth.signIn({ email, password })supabase.auth.signInWithPassword({ email, password })Method split by auth type
supabase.auth.signIn({ provider: 'google' })supabase.auth.signInWithOAuth({ provider: 'google' })OAuth separated
supabase.auth.signIn({ email })supabase.auth.signInWithOtp({ email })Magic link separated
supabase.auth.api.resetPasswordForEmail(e)supabase.auth.resetPasswordForEmail(e).api namespace removed
{ data: subscription } from onAuthStateChange{ data: { subscription } }Extra destructuring level
error.message string parsingerror.code enum (PGRST116, etc.)Reliable error matching
.single() returns error on 0 rows.maybeSingle() for optional rowsNew method for nullable results
supabase.from('t').on('INSERT', cb).subscribe()supabase.channel('c').on('postgres_changes', ...).subscribe()Realtime v2 channel API
supabase.storage.from('b').download('path')Same, but returns { data: Blob, error }Consistent error/data tuple

Realtime v2 migration detail:

// v1 realtime
supabase
  .from('messages')
  .on('INSERT', (payload) => console.log(payload.new))
  .subscribe()

// v2 realtime — channel-based API
supabase
  .channel('messages-insert')
  .on('postgres_changes', { event: 'INSERT', schema: 'public', table: 'messages' },
    (payload) => console.log(payload.new))
  .subscribe()

Step 2: Run the Upgrade and Apply Code Migrations

Create a branch, install new packages, and transform code to match v2 APIs.

# Create upgrade branch
git checkout -b upgrade-supabase-sdk

# Upgrade JS/TS SDK
npm install @supabase/supabase-js@latest

# Upgrade SSR helper (if used with Next.js/SvelteKit/Nuxt)
npm install @supabase/ssr@latest

# Upgrade CLI
npm install -g supabase@latest

# Upgrade Python SDK
pip install --upgrade supabase

# Regenerate TypeScript types from linked project
npx supabase gen types typescript --linked > lib/database.types.ts

# Generate a database migration if schema drifted
npx supabase db diff --use-migra -f upgrade_check

Apply auth code migrations:

// BEFORE (v1 auth patterns)
const session = supabase.auth.session()
const user = supabase.auth.user()
const { error } = await supabase.auth.signIn({ email, password })
const { data: subscription } = supabase.auth.onAuthStateChange(callback)

// AFTER (v2 auth patterns)
const { data: { session } } = await supabase.auth.getSession()
const { data: { user } } = await supabase.auth.getUser()
const { error } = await supabase.auth.signInWithPassword({ email, password })
const { data: { subscription } } = supabase.auth.onAuthStateChange(callback)

Apply error handling migration:

// BEFORE (v1 — string matching)
if (error.message.includes('not found')) { ... }

// AFTER (v2 — structured error codes)
if (error.code === 'PGRST116') { ... }  // "not found" → PGRST116

Step 3: Verify, Test, and Prepare Rollback

# Type check (catches 90% of migration issues)
npx tsc --noEmit

# Run test suite
npm test

# Python tests
python -m pytest tests/ -v

# Manual smoke test critical auth flows:
# 1. Sign up → confirm email → sign in with password
# 2. OAuth sign in → callback handling
# 3. Password reset → email → reset form
# 4. Session refresh across page navigations
# 5. Realtime subscription connect/disconnect
# 6. Storage upload/download round-trip

Rollback procedure (if upgrade causes issues):

# Option A: Pin to previous version
npm install @supabase/supabase-js@<previous-version>
pip install supabase==<previous-version>

# Option B: Revert the branch
git stash && git checkout main

Output

  • @supabase/supabase-js upgraded to latest version with npm list confirmation
  • All supabase.auth.signIn() calls migrated to signInWithPassword / signInWithOAuth / signInWithOtp
  • Sync auth methods (session(), user()) replaced with async getSession() / getUser()
  • Realtime subscriptions migrated from .on() to channel-based API
  • data/error destructuring updated where return shapes changed
  • TypeScript types regenerated from current schema
  • Test suite passing, type checking clean
  • Rollback branch or version pin documented

Error Handling

ErrorCauseSolution
Property 'session' does not existv1 sync .session() removed in v2Replace with await supabase.auth.getSession()
Property 'signIn' does not existsignIn split into multiple methods in v2Use signInWithPassword, signInWithOAuth, or signInWithOtp
supabase.auth.api is undefined.api namespace removed in v2Call methods directly on supabase.auth.*
TypeError: supabase.from(...).on is not a functionRealtime API replaced in v2Use supabase.channel().on('postgres_changes', ...)
Type errors after gen typesDatabase schema changed between versionsUpdate application code to match new generated types
PGRST116 error on .single()Zero rows returned (v2 throws)Use .maybeSingle() for optional lookups
ERR_REQUIRE_ESM after upgradev2 is ESM-only in some bundlersUpdate tsconfig.json to "module": "esnext" or use dynamic import()
AuthSessionMissingErrorgetSession() called before auth initializedWrap in onAuthStateChange listener or check session !== null

Examples

Full v1 → v2 auth migration (Next.js):

// lib/supabase.ts — client initialization (unchanged API)
import { createClient } from '@supabase/supabase-js'
import type { Database } from './database.types'

export const supabase = createClient<Database>(
  process.env.NEXT_PUBLIC_SUPABASE_URL!,
  process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!
)
// app/login/page.tsx — v2 auth flow
export async function login(email: string, password: string) {
  const { data, error } = await supabase.auth.signInWithPassword({
    email,
    password,
  })
  if (error) {
    // v2: use error.code instead of parsing error.message
    if (error.code === 'invalid_credentials') {
      return { success: false, message: 'Invalid email or password' }
    }
    throw error
  }
  return { success: true, session: data.session }
}
// hooks/useAuth.ts — v2 session listener
import { useEffect, useState } from 'react'
import { supabase } from '@/lib/supabase'
import type { Session } from '@supabase/supabase-js'

export function useAuth() {
  const [session, setSession] = useState<Session | null>(null)

  useEffect(() => {
    // v2: getSession is async, returns nested { data: { session } }
    supabase.auth.getSession().then(({ data: { session } }) => {
      setSession(session)
    })

    // v2: subscription nested one level deeper
    const { data: { subscription } } = supabase.auth.onAuthStateChange(
      (_event, session) => setSession(session)
    )

    return () => subscription.unsubscribe()
  }, [])

  return session
}

Python SDK upgrade:

# Before (supabase-py < 2.0)
from supabase import create_client
supabase = create_client(url, key)
data = supabase.table("users").select("*").execute()
users = data["data"]

# After (supabase-py >= 2.0)
from supabase import create_client, Client
supabase: Client = create_client(url, key)
response = supabase.table("users").select("*").execute()
users = response.data  # attribute access, not dict

Resources

  • supabase-js v2 Migration Guide — official step-by-step
  • supabase-js Releases — changelog for every version
  • Supabase CLI Releases — CLI changelog
  • Auth Helpers Migration — @supabase/auth-helpers@supabase/ssr
  • Realtime v2 Guide — channel-based API reference
  • [supabase-py Releases]

Content truncated.

Prerequisites

@supabase/supabase-js or Python `supabase` package installedGit with a clean working treeTest suite available for post-upgrade verificationNode.js >= 18 or Python >= 3.8

How it compares

This automates the upgrade process and code migration, unlike manually updating dependencies and refactoring code.

Compared to similar skills

supabase-upgrade-migration side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
supabase-upgrade-migration (this skill)127dReviewIntermediate
sql-optimization-patterns642moNo flagsAdvanced
drizzle-orm322moNo flagsIntermediate
postgres-patterns205moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

More by jeremylongshore

View all by jeremylongshore

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

ollama-setup

jeremylongshore

Configure auto-configure Ollama when user needs local LLM deployment, free AI alternatives, or wants to eliminate hosted API costs. Trigger phrases: "install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs". Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

1167

backtesting-trading-strategies

jeremylongshore

Backtest crypto and traditional trading strategies against historical data. Calculates performance metrics (Sharpe, Sortino, max drawdown), generates equity curves, and optimizes strategy parameters. Use when user wants to test a trading strategy, validate signals, or compare approaches. Trigger with phrases like "backtest strategy", "test trading strategy", "historical performance", "simulate trades", "optimize parameters", or "validate signals".

1071

generating-database-seed-data

jeremylongshore

Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.

1033

cursor-codebase-indexing

jeremylongshore

Execute set up and optimize Cursor codebase indexing. Triggers on "cursor index setup", "codebase indexing", "index codebase", "cursor semantic search". Use when working with cursor codebase indexing functionality. Trigger with phrases like "cursor codebase indexing", "cursor indexing", "cursor".

885

testing-mobile-apps

jeremylongshore

Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run iOS tests", or "validate Android functionality".

810

Search skills

Search the agent skills registry