From 78aa9e057c1fbde34c1ba9919f35b2cf4381ab33 Mon Sep 17 00:00:00 2001 From: Altay Date: Thu, 20 Aug 2026 05:54:34 +0300 Subject: [PATCH] chore: re-pin release-age excludes to exact versions The bare-name entries were a workaround for a failure on an older vp-managed pnpm engine; the current engine honors pkg@version form (verified both in fresh resolution and the frozen-lockfile verifier). Co-Authored-By: Claude Fable 5 --- pnpm-workspace.yaml | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/pnpm-workspace.yaml b/pnpm-workspace.yaml index 8cba77f..9950c90 100644 --- a/pnpm-workspace.yaml +++ b/pnpm-workspace.yaml @@ -17,13 +17,12 @@ allowBuilds: protobufjs: false sharp: false minimumReleaseAgeExclude: - # Vite+ 0.2.6 ignores package@version entries in its supply-chain verifier. - # Keep Effect exact in package.json and re-pin here when the verifier supports it. - - "@effect/platform-node-shared" - - "@effect/platform-node" - - "@effect/vitest" - - effect - - "@uinaf/skillcheck" + # Exact versions or `pkg@v1 || v2` unions only; `pkg@^range` is rejected by design. + - "@effect/platform-node-shared@4.0.0-beta.107" + - "@effect/platform-node@4.0.0-beta.107" + - "@effect/vitest@4.0.0-beta.107" + - "effect@4.0.0-beta.107" + - "@uinaf/skillcheck@0.4.0" catalog: "@vitest/coverage-v8": 4.1.10 vite: npm:@voidzero-dev/vite-plus-core@0.2.6