From a4a74218b2bc1c6c0f18dd384d20e7e43f730e2a Mon Sep 17 00:00:00 2001 From: John McLear Date: Sun, 17 May 2026 19:35:11 +0100 Subject: [PATCH] chore(deps): regenerate pnpm-lock.yaml after ep_plugin_helpers bump MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Prior package.json bump (commit `b33bcce`) left the lockfile pinned to ^0.5.x while the manifest moved to ^0.6.x. The release workflow's `pnpm i --frozen-lockfile` step has been failing ever since, blocking every npm publish — fresh installs still resolve ep_plugin_helpers@0.5.3 even though main has ^0.6.x. Regenerate the lockfile so the next push to the default branch can re-publish cleanly. Co-Authored-By: Claude Opus 4.7 (1M context) --- pnpm-lock.yaml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml index 81ddc7a..80649ea 100644 --- a/pnpm-lock.yaml +++ b/pnpm-lock.yaml @@ -9,8 +9,8 @@ importers: .: dependencies: ep_plugin_helpers: - specifier: ^0.2.7 - version: 0.2.7 + specifier: ^0.6.1 + version: 0.6.2 devDependencies: eslint: specifier: ^8.57.1 @@ -404,8 +404,8 @@ packages: resolution: {integrity: sha512-Qohcme7V1inbAfvjItgw0EaxVX5q2rdVEZHRBrEQdRZTssLDGsL8Lwrznl8oQ/6kuTJONLaDcGjkNP247XEhcA==} engines: {node: '>=10.13.0'} - ep_plugin_helpers@0.2.7: - resolution: {integrity: sha512-WgyI23UbpOu5o7tPE9GGBalS8Qo42ZH4DvqFf+WUFfKnyC0yDZ3+pdqYQUtTO2KNo1lG18RRlK3tX90DmE/haA==} + ep_plugin_helpers@0.6.2: + resolution: {integrity: sha512-CGWdFk6FG0Q0y1opoly+J4tkNpSOI2Tho4oOmaWCpMwgJxvdO4W/i5LIZQXLDSGoRCuAUKokd3H/fvEqTjztgw==} engines: {node: '>=18.0.0'} es-abstract@1.24.2: @@ -1681,7 +1681,7 @@ snapshots: graceful-fs: 4.2.11 tapable: 2.3.2 - ep_plugin_helpers@0.2.7: {} + ep_plugin_helpers@0.6.2: {} es-abstract@1.24.2: dependencies: