Fresh out of the oven

@prismicio/next v3 is a small maintenance release. It drops support for older Next.js versions and removes two APIs that were already deprecated. Everything else works the same.

The Cache Components helpers are now stable: getPreviewRef(), cacheTagPrismicPages(), revalidatePrismicPages(), and getPrismicCacheTags().

How to upgrade

If your website already uses Next.js 15 or 16, upgrading is one command:

npm install @prismicio/next@^3

If you use createLocaleRedirect() or the App Router CreateClientConfig type, replace them too. The @prismicio/next v3 upgrade guide shows how.

Next.js 13 and 14 are supported through @prismicio/next v2. However, we recommend upgrading to Next.js 16.

Prismic now fully supports SvelteKit 3 in the @prismicio/svelte SDK and the Prismic CLI. The SvelteKit guide and examples in our docs are updated too.

How to upgrade

Follow the @prismicio/svelte v3 upgrade guide.

SvelteKit 2 is supported through @prismicio/svelte v2 and the Prismic CLI. However, we recommend upgrading to SvelteKit 3.

Prismic MCP can now publish a release, and only when someone asks it to. You say it in words, something like "publish the August promo release," and it goes through only if you already have publishing rights in the repository. The agent can't do anything you couldn't do yourself.

Nothing is scheduled and nothing runs on its own. The agent never decides a release is ready, it still can't delete anything (documents are archived, not deleted), and it still stages its work as drafts. You decide what goes live.

What this unblocks

Until now, the MCP did the whole job and then stopped one step short. It staged everything as drafts, and someone had to open Prismic to push the release live. That's fine for most content work, but it meant every automated job ended in a manual step, and some of the things customers asked us for weren't possible at all. A bulk edit, a localization pass, or a migration can now run start to finish in the tool you're already working in.

Also in the Migration API

You can publish a release from the Migration API too, so it works the same whether you're in an AI tool or in your own code.

We're working on a clearer way to confirm a publish from inside the MCP. More on that soon.

The Prismic MCP docs cover setup, connection, and the full list of tools.