chore(content-freshness): test against EmDash 0.40.1

.github/workflows/compat-matrix.yml

@@ -41,7 +41,7 @@ jobs:
           cache: pnpm
       - run: pnpm install --frozen-lockfile
       - run: pnpm typecheck
-      - run: ./scripts/compat-matrix.sh 0.39.1 0.40.0
+      - run: ./scripts/compat-matrix.sh 0.39.0 0.39.1 0.40.0
 
   latest:
     name: current EmDash (informational)

AGENTS.md

@@ -43,7 +43,7 @@ pnpm install
 pnpm typecheck
 pnpm test        # emdash-plugin validate, then vitest, per package
 pnpm build
-./scripts/compat-matrix.sh 0.39.1 0.40.0   # suites against other EmDash releases
+./scripts/compat-matrix.sh 0.39.0 0.39.1 0.40.0   # suites against other EmDash releases
 ```
 
 ## Releases

packages/content-freshness/AGENTS.md

@@ -8,7 +8,7 @@ Keep `emdash-plugin.jsonc` aligned with the runtime implementation, declare ever
 `emdash` is a peer with a floor and no ceiling (`>=0.39.0`, the same as
 `env:emdash` in the manifest); the dev dependency stays below the next
 major until the toolchain is moved on purpose. Built with
-`@emdash-cms/plugin-cli@0.12.0` and `@emdash-cms/plugin-test@0.2.1`;
+`@emdash-cms/plugin-cli@0.12.0` and `@emdash-cms/plugin-test@0.2.3` (EmDash 0.40.1);
 `scripts/compat-matrix.sh` at the repository root runs the suite against
 later EmDash releases. A plain `pnpm install` at the workspace root is
 enough.

packages/content-freshness/README.md

@@ -82,16 +82,18 @@ pnpm build
 
 | EmDash | Plugin test suite |
 | ------ | ----------------- |
+| 0.40.1 | 38 passed |
+| 0.40.0 | 38 passed |
 | 0.39.1 | 38 passed |
 | 0.39.0 | 38 passed |
 
-Declared range: `emdash >=0.39.0 <1.0.0`. The table covers **every released
-version inside it** — 0.39.0 and 0.39.1 are the only ones published, so this is
-the whole range rather than a sample. 0.39.0 is the floor because the plugin
-lists collections through `schema:read`, which earlier versions do not have.
+Declared range: `emdash >=0.39.0`, with no upper bound. The table covers
+**every EmDash release since the floor**. 0.39.0 is the floor because the
+plugin lists collections through `schema:read`, which earlier versions do not
+have.
 
 Reproduce with `scripts/compat-matrix.sh` from the repo root. Last run
-2026-09-24, when 0.39.1 was the latest EmDash release. A newer EmDash than the
+2026-09-25, when 0.40.1 was the latest EmDash release. A newer EmDash than the
 table's top row is untested rather than unsupported: nothing blocks the install,
 and this table is how you tell the difference.
 

packages/content-freshness/package.json

@@ -55,7 +55,7 @@
 	"devDependencies": {
 		"@eisbachcode/emdash-plugin-shared": "workspace:*",
 		"@emdash-cms/plugin-cli": "0.12.0",
-		"@emdash-cms/plugin-test": "0.2.1",
+		"@emdash-cms/plugin-test": "0.2.3",
 		"emdash": ">=0.39.0 <1.0.0",
 		"typescript": "^5.9.0",
 		"vitest": "^4.1.0"

pnpm-workspace.yaml

@@ -21,15 +21,15 @@ allowBuilds:
 strictDepBuilds: true
 dangerouslyAllowAllBuilds: false
 minimumReleaseAgeExclude:
-  - '@emdash-cms/admin@0.39.0'
-  - '@emdash-cms/auth@0.39.0'
-  - '@emdash-cms/blocks@0.39.0'
-  - '@emdash-cms/cloudflare@0.39.0'
-  - '@emdash-cms/gutenberg-to-portable-text@0.39.0'
+  - '@emdash-cms/admin@0.39.0 || 0.40.1'
+  - '@emdash-cms/auth@0.39.0 || 0.40.1'
+  - '@emdash-cms/blocks@0.39.0 || 0.40.1'
+  - '@emdash-cms/cloudflare@0.39.0 || 0.40.1'
+  - '@emdash-cms/gutenberg-to-portable-text@0.39.0 || 0.40.1'
   - '@emdash-cms/plugin-cli@0.12.0'
-  - '@emdash-cms/plugin-test@0.2.0'
+  - '@emdash-cms/plugin-test@0.2.0 || 0.2.3'
   - '@emdash-cms/plugin-types@0.4.0'
   - '@emdash-cms/registry-client@0.6.1'
   - '@emdash-cms/registry-lexicons@0.6.0'
   - '@emdash-cms/registry-verification@0.3.2'
-  - emdash@0.39.0
+  - emdash@0.39.0 || 0.40.1