From 873b683d80a3fdb45cd002b1bb276a3858a28822 Mon Sep 17 00:00:00 2001 From: Ole Kristian Losvik Date: Sat, 1 Aug 2026 23:53:33 +0100 Subject: [PATCH] fix(eslint-config): release the corrected dependencies manifest npm's @eventuras/eslint-config@1.0.3 was published 2026-04-15 from the eventuras monorepo with all runtime packages in devDependencies, so consumers under pnpm's strict isolation cannot resolve @eslint/js and the other plugins at lint time. This repo already carries the corrected manifest (runtime packages in dependencies) but at the same version number, so changeset publish has been skipping it. A patch bump gets the fix out as 1.0.4. Co-Authored-By: Claude Fable 5 --- .changeset/republish-eslint-config.md | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 .changeset/republish-eslint-config.md diff --git a/.changeset/republish-eslint-config.md b/.changeset/republish-eslint-config.md new file mode 100644 index 0000000..dfb60b3 --- /dev/null +++ b/.changeset/republish-eslint-config.md @@ -0,0 +1,5 @@ +--- +'@eventuras/eslint-config': patch +--- + +Republish with runtime packages declared as `dependencies`. The npm 1.0.3 tarball was published from the eventuras monorepo with everything in `devDependencies`, so consumers under pnpm's strict isolation fail to resolve `@eslint/js` and the other plugins at lint time. The corrected manifest has been sitting unpublished in this repo because the version was never bumped past the already-published 1.0.3.