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".

Ir a la instalación

Repositorio: jeremylongshore/tons-of-skills-marketplace
Última actividad en el origen: 19 de agosto de 2026 a las 12:13
Idioma detectado de SKILL.md: inglés
Estrellas: 2677
Forks: 392

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill supabase-upgrade-migration

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos

4 archivos

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

langchain-deploy-integration

Deploy a LangChain 1.0 / LangGraph 1.0 app to Cloud Run, Vercel, or LangServe correctly — with timeouts sized for chain length, cold-start mitigation, SSE anti-buffering headers, and Secret Manager over .env. Use when prepping a first production deploy, debugging a stream that hangs behind a proxy, or diagnosing p99 latency spikes. Trigger with "langchain deploy", "langchain cloud run", "langchain vercel python", "langchain langserve", or "langchain docker".

2026-08-26

langchain-langgraph-agents

Build a correct LangGraph 1.0 ReAct agent with create_react_agent — typed tools, error propagation, recursion caps, and stop conditions that actually stop. Use when writing a first tool-calling agent, migrating from AgentExecutor or initialize_agent, or diagnosing an agent that loops on vague prompts. Trigger with "langgraph agent", "create_react_agent", "langgraph tool calling", "AgentExecutor migration", or "agent loop cost".

2026-08-26

langchain-langgraph-human-in-loop

Build LangGraph 1.0 human-in-the-loop approval flows with interrupt_before / interrupt_after and Command(resume=...) — JSON-serializable state, clean resume semantics, and UI wiring for approval decisions. Use when adding an approval gate before an expensive tool call, wiring a Slack/web UI for agent approvals, or debugging a graph that crashes on interrupt. Trigger with "langgraph human in loop", "langgraph interrupt_before", "langgraph approval flow", "Command resume", "langgraph HITL".

2026-08-26

Ver todos los de este repositorio

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

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

Opciones de instalación

Revisa los archivos de origen

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

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

Supabase Upgrade Migration

Overview

Current State

Prerequisites

Instructions

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

Más de este repositorio

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