supabase-upgrade-migration

Upgrade Supabase SDK and CLI versions with breaking-change detection and automated code migration. Use when upgrading @supabase/supabase-js (v1→v2 or minor bumps), migrating auth/realtime/storage APIs, or updating the Supabase CLI. Trigger with phrases like "upgrade supabase", "supabase breaking changes", "migrate supabase v2", "update supabase SDK".

Aller à l'installation

Dépôt: jeremylongshore/claude-code-plugins-plus-skills
Dernière activité de la source: 19 juillet 2026 à 02:55
Langue détectée de SKILL.md: anglais
Étoiles: 2 604
Forks: 378

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill supabase-upgrade-migration

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Explorateur de fichiers

4 fichiers

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’installation

clerk-core-workflow-a

Implement user sign-up and sign-in flows with Clerk. Use when building authentication UI, customizing sign-in experience, or implementing OAuth social login. Trigger with phrases like "clerk sign-in", "clerk sign-up", "clerk login flow", "clerk OAuth", "clerk social login".

2026-07-23

clerk-core-workflow-b

Implement session management and middleware with Clerk. Use when managing user sessions, configuring route protection, or implementing token refresh and custom JWT templates. Trigger with phrases like "clerk session", "clerk middleware", "clerk route protection", "clerk token", "clerk JWT".

2026-07-23

clerk-enterprise-rbac

Configure enterprise SSO, role-based access control, and organization management. Use when implementing SSO integration, configuring role-based permissions, or setting up organization-level controls. Trigger with phrases like "clerk SSO", "clerk RBAC", "clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations".

2026-07-23

Tout voir dans ce dépôt

name	supabase-upgrade-migration
description	Upgrade Supabase SDK and CLI versions with breaking-change detection and automated code migration. Use when upgrading @supabase/supabase-js (v1→v2 or minor bumps), migrating auth/realtime/storage APIs, or updating the Supabase CLI. Trigger with phrases like "upgrade supabase", "supabase breaking changes", "migrate supabase v2", "update supabase SDK".
allowed-tools	Read, Write, Edit, Bash(npm:), Bash(npx:), Bash(pip:), Bash(supabase:), Bash(git:*), Grep, Glob
version	1.53.0
license	MIT
author	Jeremy Longshore <jeremy@intentsolutions.io>
tags	["saas","supabase","migration","upgrade","sdk"]
compatibility	Designed for Claude Code, also compatible with Codex and OpenClaw

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 Pattern

`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 parsing	`error.code` enum (`PGRST116`, etc.)	Reliable error matching
`.single()` returns error on 0 rows	`.maybeSingle()` for optional rows	New 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

Error	Cause	Solution
`Property 'session' does not exist`	v1 sync `.session()` removed in v2	Replace with `await supabase.auth.getSession()`
`Property 'signIn' does not exist`	`signIn` split into multiple methods in v2	Use `signInWithPassword`, `signInWithOAuth`, or `signInWithOtp`
`supabase.auth.api` is undefined	`.api` namespace removed in v2	Call methods directly on `supabase.auth.*`
`TypeError: supabase.from(...).on is not a function`	Realtime API replaced in v2	Use `supabase.channel().on('postgres_changes', ...)`
Type errors after `gen types`	Database schema changed between versions	Update 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 upgrade	v2 is ESM-only in some bundlers	Update `tsconfig.json` to `"module": "esnext"` or use dynamic `import()`
`AuthSessionMissingError`	`getSession()` called before auth initialized	Wrap in `onAuthStateChange` listener or check `session !== null`

supabase-upgrade-migration

Options d'installation

Vérifiez les fichiers source

Supabase Upgrade Migration

Overview

Current State

Prerequisites

Instructions

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

Supabase Upgrade Migration

Overview

Current State

Prerequisites

Instructions

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

Step 2: Run the Upgrade and Apply Code Migrations

Step 3: Verify, Test, and Prepare Rollback

Output

Error Handling

Examples

Resources

Next Steps

supabase-upgrade-migration

Informations de source

Options d'installation

Vérifiez les fichiers source

Plus depuis ce dépôt

Plus depuis ce dépôt

Supabase Upgrade Migration

Overview

Current State

Prerequisites

Instructions

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

Supabase Upgrade Migration

Overview

Current State

Prerequisites

Instructions

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

Step 2: Run the Upgrade and Apply Code Migrations

Step 3: Verify, Test, and Prepare Rollback

Output

Error Handling

Examples

Resources

Next Steps