prisma-next-extension-upgrade

Name: prisma-next-extension-upgrade
Availability: InStock
Author: Prisma

Upgrade Prisma Next dependencies and apply SPI migration logic for extensions.

47.5k|2.5k|Updated Jun 20, 2019

Search Tags:#typescript #dependency management #migration #extension #upgrade #prisma

Ready to run

npx skills add https://github.com/prisma/prisma --skill prisma-next-extension-upgrade

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prisma-next-extension-upgrade
Source: https://github.com/prisma/prisma/tree/main/skills/extension-author/prisma-next-extension-upgrade
Command: npx skills add https://github.com/prisma/prisma --skill prisma-next-extension-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tsx, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the complex, multi-step process of upgrading Prisma Next extensions, ensuring dependency pins are exact and SPI-breaking changes are handled correctly.

Core Features & Use Cases

Automated Version Bumping: Safely advances @prisma-next/* dependencies across minor versions while maintaining exact-pin requirements.
SPI Migration: Executes per-transition upgrade instructions, including codemods and manual migration steps, to keep extensions compatible with the latest framework SPI.
Use Case: When a new Prisma Next minor version is released, use this Skill to automatically update your extension's dependencies, run necessary type-level and runtime migrations, and verify the integrity of your contract definitions.

Quick Start

Ask the agent to upgrade Prisma Next to the latest version in your extension repository.

Frequently Asked Questions about prisma-next-extension-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I upgrade Prisma Next extension dependencies across minor versions?▼

To upgrade Prisma Next extension dependencies, you can automate the process by bumping `@prisma-next/*` packages across minor versions while maintaining exact-pin requirements and executing necessary SPI migration logic.

What is SPI migration and when do I need it for Prisma Next extensions?▼

SPI migration is the process of applying per-transition upgrade instructions, including codemods and manual steps, to keep Prisma Next extensions compatible with the latest framework contract, middleware, and migration surfaces.

How do I ensure exact version pins when updating Prisma Next framework packages?▼

You can ensure exact version pins during a Prisma Next upgrade by using automated validation to verify dependency pins, apply transition chain bumps, and execute commit cycles for framework compatibility.

Can I automate codemods and type-level migrations for Prisma Next extensions?▼

Yes, you can automate codemods and type-level migrations for Prisma Next extensions by executing per-transition upgrade instructions that validate contract definitions and ensure extension compatibility with the framework.

Do I need TypeScript to run Prisma Next extension upgrade scripts?▼

Yes, you need a TypeScript environment to run Prisma Next extension upgrade scripts, as the migration logic and dependency management rely on TypeScript and the `tsx` runtime executor.

Why are my Prisma Next extension migrations failing after a minor version bump?▼

Prisma Next extension migrations may fail after a minor version bump if SPI-breaking changes are not handled correctly, requiring automated validation and per-transition migration instructions to verify contract integrity.