@emplugins/emprivacy 2.1.0 → 3.0.0

package/README.md

@@ -27,7 +27,7 @@
 
 ## Requirements
 
-- **EmDash** `^0.38.0` (**tested with `0.38.0`**; re-test on your deployed minor when upgrading).
+- **EmDash** `^1.0.1` (**tested with `1.0.1`**). EmDash 0.x is not supported.
 - **Node.js** `>= 22.16` (matches EmDash’s engine requirement).
 - Register as a **native** plugin in **`astro.config`** via `plugins: []` (not `sandboxed: []`). EmPrivacy uses `page:fragments` for the public banner and `componentsEntry` for embed placeholders. See [Page fragments](https://docs.emdashcms.com/plugins/creating-native-plugins/page-fragments/) and [Plugin overview](https://docs.emdashcms.com/plugins/overview/).
 
@@ -41,7 +41,7 @@ npm install @emplugins/emprivacy
 
 Published under the [emplugins](https://www.npmjs.com/org/emplugins) npm org. Source: [github.com/EmPlugins/EmPrivacy](https://github.com/EmPlugins/EmPrivacy). See [EMDASH_COMPAT.md](./EMDASH_COMPAT.md) for EmDash version mapping.
 
-Use a **semver range** if you want controlled upgrades, for example `@emplugins/emprivacy@^1.0.0`. Versioning: [docs/RELEASES.md](docs/RELEASES.md). Org publish: [docs/NPM_ORG_PUBLISH.md](docs/NPM_ORG_PUBLISH.md).
+Use a **semver range** if you want controlled upgrades, for example `@emplugins/emprivacy@^3.0.0`. Versioning: [docs/RELEASES.md](docs/RELEASES.md). Org publish: [docs/NPM_ORG_PUBLISH.md](docs/NPM_ORG_PUBLISH.md).
 
 The legacy unscoped package `emprivacy` is deprecated; migrate imports to `@emplugins/emprivacy`.
 

package/dist/index.mjs

@@ -1463,7 +1463,7 @@ function buildVendorList(cfg) {
 }
 //#endregion
 //#region src/version.ts
-const VERSION = "2.1.0";
+const VERSION = "3.0.0";
 //#endregion
 //#region src/runtime.ts
 /** Soft cap for anonymous consent POSTs per client fingerprint per UTC hour. */
@@ -1770,7 +1770,7 @@ function createPlugin() {
 }
 async function buildSettingsPage(ctx) {
 	const [cfg, latestPublished] = await Promise.all([loadConfig(ctx), fetchLatestPublishedVersion({ fetch: ctx.http?.fetch ?? globalThis.fetch })]);
-	const installedVersion = ctx.plugin?.version ?? "2.1.0";
+	const installedVersion = ctx.plugin?.version ?? "3.0.0";
 	const analyticsText = cfg.analyticsScriptUrls.map((src) => {
 		const i = cfg.scriptIntegrity[src];
 		return i ? `${src} ${i}` : src;

package/docs/DEVELOPMENT.md

@@ -25,7 +25,7 @@ pnpm run build
 
 The full install (including the `emdash` **dev** tree) can report transitive advisories from EmDash’s tooling stack. Those are owned by the site’s EmDash upgrade path, not by EmPrivacy’s published tarball.
 
-**This repository pins Kysely** via `pnpm.overrides` in `package.json` (currently `0.29.6`, aligned with EmDash 0.38). Regenerate the lockfile with `pnpm install` after changing overrides.
+**This repository pins Kysely** via `pnpm.overrides` in `package.json` (currently `0.29.6`, aligned with EmDash 1.0.1). Regenerate the lockfile with `pnpm install` after changing overrides.
 
 ## Deprecation warnings you may still see
 

package/docs/GETTING_STARTED.md

@@ -21,7 +21,7 @@ This guide is for **EmDash site managers** who want cookie consent on a live sit
 
 ## Before you begin
 
-1. An EmDash site on **`emdash@^0.38.0`** with the EmDash Astro integration in `astro.config`.
+1. An EmDash site on **`emdash@^1.0.1`** with the EmDash Astro integration in `astro.config`. EmDash 0.x is not supported.
 2. Ability to edit **`astro.config`** and redeploy (or run locally).
 3. Register EmPrivacy as a **native** plugin (`plugins: []`, not `sandboxed: []`).
 
@@ -35,7 +35,7 @@ pnpm add @emplugins/emprivacy
 npm install @emplugins/emprivacy
 ```
 
-Pin a line with a range such as `@emplugins/emprivacy@^1.0.0`. See [RELEASES.md](./RELEASES.md).
+Pin a line with a range such as `@emplugins/emprivacy@^3.0.0`. See [RELEASES.md](./RELEASES.md).
 
 ---
 

package/docs/RELEASES.md

@@ -25,7 +25,7 @@ These guards keep published tarballs consistent with `package.json` and avoid sh
 - **`dist/` is not committed** — It is listed in `.gitignore`. Build artifacts are produced locally, in CI, and **immediately before publish** via `prepublishOnly`.
 - **`prepublishOnly`** — Runs `sync:version` (keeps `src/version.ts` aligned with `package.json`), `typecheck`, `build`, `test`, **`verify:exports`**, and `pnpm audit`.
 - **`kysely` override** — The dev-dependency `emdash` can resolve an older `kysely`; `pnpm.overrides` in `package.json` pins a **patched** Kysely so `pnpm audit` stays clean. See [docs/DEVELOPMENT.md](DEVELOPMENT.md).
-- **Install range** — Pin consumers with semver as needed, e.g. `@emplugins/emprivacy@^1.0.0`.
+- **Install range** — Pin consumers with semver as needed, e.g. `@emplugins/emprivacy@^3.0.0`. Requires EmDash `^1.0.1`.
 
 Before publishing locally (usually unnecessary once CI is configured):
 
@@ -77,5 +77,5 @@ See [EMDASH_COMPAT.md](../EMDASH_COMPAT.md) for tested upstream versions and upg
 Pin with a range that matches your risk tolerance, for example:
 
 ```bash
-pnpm add @emplugins/emprivacy@^1.0.0
+pnpm add @emplugins/emprivacy@^3.0.0
 ```

package/docs/RELEASE_NOTES.md

@@ -6,6 +6,13 @@
 
 _(none)_
 
+# emprivacy v3.0.0
+
+## Changes
+
+- **EmDash 1.0 baseline** — Requires **`emdash@^1.0.1`** (tested with **`1.0.1`**). EmDash 0.x is not supported. Sites still on EmDash 0.38 should stay on `@emplugins/emprivacy@2`.
+- Remains a **native** plugin: `format: "native"`, named `createPlugin()`, `page:fragments`, and Portable Text embed placeholders. Register `emprivacyPlugin()` in `plugins: []`. The official plugin registry only accepts sandboxed plugins, so this package stays on npm.
+
 # emprivacy v2.1.0
 
 ## Changes

package/docs/TESTING.md

@@ -16,7 +16,7 @@ These scripts do **not** start EmDash or drive a browser.
 
 ## Manual integration QA (required before production)
 
-Use a **staging** EmDash Astro app on **`emdash@^0.38.0`** with `emprivacyPlugin()` in **`plugins: []`**, layout wires (`EmDashHead` / body components with page context), and the same EmDash version you plan to ship.
+Use a **staging** EmDash Astro app on **`emdash@^1.0.1`** with `emprivacyPlugin()` in **`plugins: []`**, layout wires (`EmDashHead` / body components with page context), and the same EmDash version you plan to ship. EmDash 0.x is not supported.
 
 ### Core flows
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "//": "SPDX-License-Identifier: MIT",
   "name": "@emplugins/emprivacy",
-  "version": "2.1.0",
+  "version": "3.0.0",
   "description": "Cookie consent, gated embeds, and privacy notices for EmDash (GDPR, CCPA/CIPA-oriented configuration)",
   "type": "module",
   "main": "dist/index.mjs",
@@ -39,14 +39,14 @@
   "license": "MIT",
   "packageManager": "pnpm@9.15.4",
   "peerDependencies": {
-    "emdash": "^0.38.0"
+    "emdash": "^1.0.1"
   },
   "dependencies": {
     "zod": "4.6.5"
   },
   "devDependencies": {
     "@changesets/cli": "^3.0.3",
-    "emdash": "0.38.0",
+    "emdash": "^1.0.1",
     "tsdown": "^0.23.0",
     "typescript": "^5.9.3",
     "vitest": "^5.0.1"