plugin-field-kit peer-dependency issue

[a-man-called-q]

Description

As I check the npm, it still has "@cloudflare/kumo": "^1.0.0",

Apparently Github Action has issues with that

Steps to reproduce

run it with github action

Environment

• emdash : 0.30.0
• node : 24.0.0

Logs / error output

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @emdash-cms/plugin-field-kit@0.1.0
npm error Found: @cloudflare/kumo@2.6.0
npm error node_modules/@cloudflare/kumo
npm error   @cloudflare/kumo@"2.6.0" from @emdash-cms/admin@0.30.0
npm error   node_modules/@emdash-cms/admin
npm error     @emdash-cms/admin@"0.30.0" from emdash@0.30.0
npm error     node_modules/emdash
npm error       emdash@"^0.30.0" from the root project
npm error       2 more (@emdash-cms/cloudflare, @emdash-cms/plugin-field-kit)
npm error   @cloudflare/kumo@"2.6.0" from @emdash-cms/blocks@0.30.0
npm error   node_modules/@emdash-cms/blocks
npm error     @emdash-cms/blocks@"0.30.0" from @emdash-cms/admin@0.30.0
npm error     node_modules/@emdash-cms/admin
npm error       @emdash-cms/admin@"0.30.0" from emdash@0.30.0
npm error       node_modules/emdash
npm error         emdash@"^0.30.0" from the root project
npm error         2 more (@emdash-cms/cloudflare, @emdash-cms/plugin-field-kit)
npm error
npm error Could not resolve dependency:
npm error peer @cloudflare/kumo@"^1.0.0" from @emdash-cms/plugin-field-kit@0.1.0
npm error node_modules/@emdash-cms/plugin-field-kit
npm error   @emdash-cms/plugin-field-kit@"^0.1.0" from the root project
npm error
npm error Conflicting peer dependency: @cloudflare/kumo@1.19.0
npm error node_modules/@cloudflare/kumo
npm error   peer @cloudflare/kumo@"^1.0.0" from @emdash-cms/plugin-field-kit@0.1.0
npm error   node_modules/@emdash-cms/plugin-field-kit
npm error     @emdash-cms/plugin-field-kit@"^0.1.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /home/runner/.npm/_logs/2026-08-02T14_24_31_554Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-08-02T14_24_31_554Z-debug-0.log

[ascorbic]

@emdashbot investigate

[emdashbot]

Completed

Investigate plugin-field-kit peer dependency conflict with @cloudflare/kumo

• Classify issue as build/package dependency bug
• Find plugin-field-kit package.json and dependency declarations
• Reproduce dependency conflict via npm/pnpm
• Diagnose root cause of peer dependency mismatch
• Verify whether this is a bug or intended

Outcome: The published `@emdash-cms/plugin-field-kit@0.1.0` package on npm has a stale peer-dependency range for `@cloudflare/kumo` (`^1.0.0`) that conflicts with the `2.6.0` required by `emdash@0.30.0` and the rest of the first-party monorepo.

Evidence in this checkout:

• `npm view @emdash-cms/plugin-field-kit@0.1.0 peerDependencies` returns `"@cloudflare/kumo": "^1.0.0"` (registry metadata reproduced).
• `packages/plugins/field-kit/package.json` currently declares `"@cloudflare/kumo": "catalog:"` under `peerDependencies` (line 24).
• `pnpm-workspace.yaml` catalog pins `@cloudflare/kumo: 2.6.0`.
• Running `pnpm pack --filter @emdash-cms/plugin-field-kit` produces a tarball whose `package.json` peerDependencies resolves `@cloudflare/kumo` to `2.6.0`, proving the source tree is already correct and a fresh publish would fix the mismatch.
• Fresh `npm install emdash@^0.30.0 @emdash-cms/plugin-field-kit@^0.1.0` resolves two copies of Kumo (`1.19.0` under the plugin vs `2.6.0` under `@emdash-cms/admin`/`@emdash-cms/blocks`), confirming the conflicting peer ranges reach the user's dependency tree; npm may or may not ERESOLVE depending on the exact hoisting shape and npm version, but the root defect is the mismatched peer range.

Root cause: the plugin was published once at version `0.1.0` when the workspace catalog still resolved `@cloudflare/kumo` to `^1.x`; the catalog has since been bumped to `2.6.0`, but no new version of `@emdash-cms/plugin-field-kit` has been cut or published, so npm still serves the old metadata.

Fix path: add a changeset for `@emdash-cms/plugin-field-kit` (patch or minor) so Changesets bumps its version and the next publish includes the updated `2.6.0` peer-dependency range. Consider also adding `@emdash-cms/plugin-field-kit` to the `fixed` versioning group in `.changeset/config.json` so future monorepo dependency bumps keep it in sync automatically.

Classification: build / package-publishing bug.

Mode: diagnose

View live dashboard · Run: 0f617fd4-e127-4eca-b72c-22ddb7f9b927

[ascorbic]

@emdashbot fix

[emdashbot]

Completed

Add a changeset for @emdash-cms/plugin-field-kit so the next publish uses the catalog-resolved @cloudflare/kumo 2.6.0 peer range instead of the stale ^1.0.0 range.

• Add changeset for plugin-field-kit peer dependency fix
• Optionally add plugin to changeset fixed group — skipped
• Verify changes with changeset status and lint

Outcome: Added `.changeset/fix-field-kit-kumo-peer-dep.md` to bump `@emdash-cms/plugin-field-kit` with a patch release. The current source already resolves `@cloudflare/kumo` through `pnpm-workspace.yaml` catalog to `2.6.0`, but the published `0.1.0` tarball still advertises `^1.0.0`, which conflicts with the `2.6.0` required by `emdash@0.30.0`/`@emdash-cms/admin`/`@emdash-cms/blocks`.

Verification:

• `npm view @emdash-cms/plugin-field-kit@0.1.0 peerDependencies` shows `@cloudflare/kumo: ^1.0.0` (reproduced stale published metadata).
• `pnpm changeset status` lists `@emdash-cms/plugin-field-kit` in the patch-bump set.
• `pnpm pack --filter @emdash-cms/plugin-field-kit` produces a tarball whose `package.json` has `@cloudflare/kumo: "2.6.0"`, proving the next publish will fix the mismatch.
• `pnpm lint:json` and `pnpm format:check` both pass.

I did not add the plugin to `.changeset/config.json` `fixed` group because that would force version-synchronization with packages already at `0.30.0`, unnecessarily jumping the plugin from `0.1.0`. That synchronization is a separate maintainer decision and out of scope for this peer-dependency fix.

Candidate branch: `bot/fix-2323`.

Mode: fix

View live dashboard · Run: 9d808066-a3a8-47fc-b230-efa98fa3d67e

[emdashbot]

A candidate change is ready to preview.

Added .changeset/fix-field-kit-kumo-peer-dep.md to bump @emdash-cms/plugin-field-kit with a patch release. The current source already resolves @cloudflare/kumo through pnpm-workspace.yaml catalog to 2.6.0, but the published 0.1.0 tarball still advertises ^1.0.0, which conflicts with the 2.6.0 required by emdash@0.30.0/@emdash-cms/admin/@emdash-cms/blocks.

Verification:

• npm view @emdash-cms/plugin-field-kit@0.1.0 peerDependencies shows @cloudflare/kumo: ^1.0.0 (reproduced stale published metadata).
• pnpm changeset status lists @emdash-cms/plugin-field-kit in the patch-bump set.
• pnpm pack --filter @emdash-cms/plugin-field-kit produces a tarball whose package.json has @cloudflare/kumo: "2.6.0", proving the next publish will fix the mismatch.
• pnpm lint:json and pnpm format:check both pass.

I did not add the plugin to .changeset/config.json fixed group because that would force version-synchronization with packages already at 0.30.0, unnecessarily jumping the plugin from 0.1.0. That synchronization is a separate maintainer decision and out of scope for this peer-dependency fix.

Candidate branch: bot/fix-2323.

Try the change against your own site:

npm i https://pkg.pr.new/emdash@bot/fix-2323

Or try the candidate in a ready-to-use playground:

Open the playground preview

@a-man-called-q could you try this? Reply @emdashbot confirm if it works as requested, or @emdashbot reject <details> if it does not.

_{Maintainers can use the same commands on the reporter's behalf. Confirmation opens a draft PR; rejection reaps the branch for revision.}

Fix branch: bot/fix-2323 · Artifacts branch: bot/artifacts-2323