@plutocms/supabase 0.17.0 → 0.18.0

package/.env.example

@@ -11,6 +11,6 @@ SUPABASE_KEY=
 # environment). With the service role key above AND a working mail driver,
 # invites go out through Pluto mail, not through Supabase's mailer. Set these
 # in the environment of the running server. See the `mail` skill of
-# @plutocms/pluto for every variable.
+# @plutocms/core for every variable.
 # NUXT_PLUTO_MAIL_RESEND_API_KEY=
 # NUXT_PLUTO_MAIL_FROM="Your Site <hello@your-domain.com>"

package/CHANGELOG.md

@@ -1,5 +1,16 @@
 # Changelog
 
+## [0.18.0](https://github.com/plutocms/supabase/compare/v0.17.0...v0.18.0) (2026-10-30)
+
+
+### ⚠ BREAKING CHANGES
+
+* the layer extends @plutocms/core >=0.38.0, not @plutocms/pluto. PLUTO_PLUTO_PATH is now PLUTO_CORE_PATH.
+
+### Features
+
+* extend @plutocms/core ([#143](https://github.com/plutocms/supabase/issues/143)) ([6cefcc4](https://github.com/plutocms/supabase/commit/6cefcc4e84c2d00046f11db8b30e9f4d4ac51e12))
+
 ## [0.17.0](https://github.com/plutocms/supabase/compare/v0.16.0...v0.17.0) (2026-10-30)
 
 

package/FEATURES.md

@@ -15,7 +15,7 @@ policies shared by every project here.
   link, roles editor), invites through Pluto mail, and a guide for the Supabase sign-in emails.
   @.claude/skills/users-and-roles/SKILL.md
 - Content adapter: a Supabase/PostgREST-backed `PlutoContentAdapter`, plugging any layer's
-  declared content type into `@plutocms/pluto`'s generic content routes. It supports query
+  declared content type into `@plutocms/core`'s generic content routes. It supports query
   filters, puts the timestamps on items, and reads the public API of core with an anonymous client.
   @.claude/skills/content-adapter/SKILL.md
 - Auth driver: plugs Supabase sign-in into the admin shell that pluto core owns (navbar, sign-in

package/README.md

@@ -14,7 +14,7 @@ SUPABASE_URL=your-supabase-url
 SUPABASE_KEY=your-publishable-supabase-key
 ```
 
-2. Install the layer. It brings `@nuxtjs/supabase`, `@plutocms/pluto` and `@plutocms/utils`, so you do not add them:
+2. Install the layer. It brings `@nuxtjs/supabase`, `@plutocms/core` and `@plutocms/utils`, so you do not add them:
 
 ```bash
 npm i @plutocms/supabase
@@ -98,7 +98,7 @@ NUXT_PLUTO_MAIL_FROM="Your Site <hello@your-domain.com>"
 ```
 
 `Settings > Email` in the admin guides the setup (account, key, domain, test email). The
-`mail` skill of `@plutocms/pluto` lists every `NUXT_PLUTO_MAIL_*` variable. If the send fails,
+`mail` skill of `@plutocms/core` lists every `NUXT_PLUTO_MAIL_*` variable. If the send fails,
 the user and the roles stay, and the admin gets the invite link to send by hand.
 
 With the key, an admin can also copy the invite link (Users, then the row menu, or the invite

package/app/plugins/pluto-extension.ts

@@ -102,7 +102,7 @@ export default defineNuxtPlugin(() => {
   definePlutoExtension({
     id: 'supabase',
     // Core renders the navbar, the login page and the route guard from this
-    // driver. See the admin-shell skill in @plutocms/pluto.
+    // driver. See the admin-shell skill in @plutocms/core.
     authDriver: {
       id: 'supabase-auth',
       // The JWT claims carry the id (`sub`) and the user metadata.

package/nuxt.config.ts

@@ -1,8 +1,8 @@
 import type { PlutoMigrationFile } from './shared/types/migrations'
 
-// Point these at a local checkout (e.g. `../pluto`, `../utils`) to test
+// Point these at a local checkout (e.g. `../pluto/packages/core`, `../utils`) to test
 // unpublished changes; unset, they resolve to the published npm packages.
-const plutoLayer = process.env.PLUTO_PLUTO_PATH || '@plutocms/pluto'
+const coreLayer = process.env.PLUTO_CORE_PATH || '@plutocms/core'
 const utilsLayer = process.env.PLUTO_UTILS_PATH || '@plutocms/utils'
 
 // The host of the Supabase project, at build time. `@nuxt/image` may only read
@@ -16,7 +16,7 @@ function supabaseHost(): string {
 }
 
 export default defineNuxtConfig({
-  extends: [[plutoLayer, { install: true }], utilsLayer],
+  extends: [[coreLayer, { install: true }], utilsLayer],
 
   modules: ['@nuxt/eslint', '@nuxtjs/supabase'],
 

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "@plutocms/supabase",
   "type": "module",
-  "version": "0.17.0",
+  "version": "0.18.0",
   "trustedDependencies": [
     "@parcel/watcher",
-    "@plutocms/pluto",
+    "@plutocms/core",
     "@plutocms/utils",
     "esbuild",
     "supabase",
@@ -39,7 +39,7 @@
     "@nuxt/eslint": "^1.17.0",
     "@nuxt/ui": "^4.12.0",
     "@nuxtjs/supabase": "^2.1.0",
-    "@plutocms/pluto": ">=0.36.0 <1.0.0",
+    "@plutocms/core": ">=0.38.0 <1.0.0",
     "@plutocms/utils": ">=0.3.0 <1.0.0",
     "@supabase/supabase-js": "^2.117.3",
     "postgres": "^3.4.9",

package/server/plugins/media-driver.ts

@@ -1,6 +1,6 @@
 /**
  * Registers the Supabase media driver with the core media library, at Nitro
- * startup. See the media skill of `@plutocms/pluto`.
+ * startup. See the media skill of `@plutocms/core`.
  */
 export default defineNitroPlugin(() => {
   registerMediaDriver(createSupabaseMediaDriver())

package/server/utils/media-driver.ts

@@ -87,7 +87,7 @@ function numericIds(ids: string[]): number[] {
  * Security checks the capabilities again (`has_capability`). New files go to
  * `media/<yyyy>/<mm>/<name>-<suffix>.<ext>`, and their previews next to them
  * (`db/migrations/010_media_preview.sql`). See the media skill of
- * `@plutocms/pluto`.
+ * `@plutocms/core`.
  */
 export function createSupabaseMediaDriver(): PlutoMediaDriver {
   async function readRow(client: SupabaseClient, id: string): Promise<MediaRow> {

package/server/utils/validate.ts

@@ -4,7 +4,7 @@ import type { ZodSchema } from 'zod'
 /**
  * One field-level validation error.
  *
- * Matches `ContentValidationError` from `@plutocms/pluto`'s
+ * Matches `ContentValidationError` from `@plutocms/core`'s
  * `shared/utils/content-validate.ts`, so a zod failure and a content-model
  * failure look the same to a caller.
  */
@@ -17,7 +17,7 @@ export interface ValidationError {
  * Reads a request body and checks it against a zod schema.
  *
  * On success, returns the parsed, typed body. On failure, throws the same
- * 400 shape `@plutocms/pluto`'s generic content routes throw for a content
+ * 400 shape `@plutocms/core`'s generic content routes throw for a content
  * validation failure: `{ statusCode: 400, statusMessage: 'Validation
  * failed.', data: { errors } }`, with `errors` as `{ field, message }[]`.
  * Every route in this workspace should call this helper instead of

package/tailwind.lint.css

@@ -6,4 +6,4 @@
  */
 @import 'tailwindcss';
 @import '@nuxt/ui';
-@import '@plutocms/pluto/app/assets/css/pluto-layer.css';
+@import '@plutocms/core/app/assets/css/pluto-layer.css';