Repository navigation
chore(content-freshness): test against EmDash 0.40.1 - #9
Merged
Merged
Conversation
… plugins Copied unchanged from the proof-of-concept repository at ef4884d, where the content plugins use them: `chain.ts` carries a sweep across cron runs with alternating one-shot follow-ups, and `listCollections()` finds every collection through `schema:read`. `parseCollections()` stays for now. The floor rises to 0.39.0 because `ctx.schema` first exists there; the analytics plugin already requires 0.39.0.
Imported from the proof-of-concept repository at ef4884d as fresh files. A scheduled, network-free audit: overdue schedules, missing or badly sized SEO descriptions, stale entries, forgotten drafts, and routable collections without a URL pattern. Capabilities `content:read` and `schema:read`; it reports and never edits. Aligned with the workspace on the way in: `registry:publish` and `registry:login` instead of the generated `publish` and `login`, `prepublishOnly` builds, repository metadata for trusted publishing, a peer range with a floor and no ceiling, and the analytics plugin's vitest limits (30 s timeouts, one test file at a time). Toolchain unchanged from the proof of concept: plugin-cli 0.12.0, plugin-test 0.2.1, EmDash 0.39.1.
The full-audit test pinned the host's scheduler clock to 04:00:05 on 2026-09-25, but the plugin schedules its follow-up runs from `Date.now()`. While that night lay ahead of the real time, follow-ups fell due; since then they land after the host's clock, never run, and the sweep never finishes. The test now uses tomorrow's night, which is always ahead of the wall clock. It still fails if a follow-up is lost.
plugin-test 0.2.3 pins EmDash 0.40.1, so the suite's baseline moves from 0.39.1 to the current release. The peer floor stays at 0.39.0: every API the plugin uses exists there. `shared` takes its EmDash types from its own dev dependency. Left on 0.39.1, its `PluginContext` rejected the plugin's 0.40.1 one, because 0.40 added the `blocks` field type, so it resolves 0.40.1 as well. `shared` imports EmDash for types only; analytics keeps its own toolchain and still typechecks. pnpm added the 0.40.1 packages to minimumReleaseAgeExclude itself, as it did for 0.39.0.
The gating job ran each suite on its harness's own EmDash plus 0.39.1 and 0.40.0. That covered the floor only while every harness pinned 0.39.0. content-freshness now runs on plugin-test 0.2.3, which pins 0.40.1, so 0.39.0, the floor both plugins declare, joins the list.
…s-import # Conflicts: # pnpm-lock.yaml
…ness-emdash-0.40 # Conflicts: # pnpm-lock.yaml
…ss-emdash-0.40 # Conflicts: # packages/content-freshness/AGENTS.md # packages/content-freshness/README.md # packages/content-freshness/package.json # pnpm-lock.yaml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves content-freshness's test toolchain to the current EmDash release. Stacked on #8. Merge #8 first with a merge commit, as usual here. A squash merge would make this PR show #8's commits again. Then delete #8's branch, and GitHub retargets this PR to
main. The repository doesn't delete merged branches automatically.Changes
@emdash-cms/plugin-test0.2.1 → 0.2.3, which pins EmDash 0.40.1. The suite's baseline moves from 0.39.1 to 0.40.1. The peer floor stays at>=0.39.0: every API the plugin uses exists in 0.39.0.sharedtakes its EmDash types from its own install, and on 0.39.1 itsPluginContextrejected the plugin's 0.40.1 one, because 0.40 added theblocksfield type.sharedimports EmDash for types only. analytics keeps its toolchain (plugin-test 0.2.0) and still typechecks.minimumReleaseAgeExcludeitself on the explicitpnpm add, as it did for 0.39.0. They were published today, so they are younger than pnpm 11's default release-age minimum.Verified
scripts/compat-matrix.sh 0.39.0 0.39.1 0.40.0locally:pnpm typecheckpasses for all three packages, andshared16/16.