Pin pnpm to 11.11.0 via packageManager field#212
Merged
Conversation
CI's pnpm/action-setup step used a floating `version: 11`, which today
resolved to the newly released pnpm 11.12.0. That release's self-installer
crashes ("Cannot use 'in' operator to search for 'integrity' in undefined"
in lockfileToDepGraph/createFullPkgId), failing the frontend Lint job
(and any frontend-using workflow) before linting ever runs.
Add a `packageManager: pnpm@11.11.0` field to web/package.json and point
action-setup at it via `package_json_file: web/package.json`, omitting the
floating version. CI and local corepack now share one pinned pnpm version,
so a bad future pnpm release can no longer break CI.
Assisted-by: Claude-Code:GLM-5.2
The Lint workflow ran `pnpm dlx vue-tsc -b`, which fetches the latest vue-tsc and resolves its typescript peer dependency to the newest typescript published on npm. typescript 7.0.2 removed `./lib/tsc` from its `exports` map, so vue-tsc 3.3.7 crashes with ERR_PACKAGE_PATH_NOT_EXPORTED — breaking the type check regardless of the repo's own typescript pin. vue-tsc is already a devDependency (and the project pins typescript ~5.9.3), so run `pnpm exec vue-tsc -b` to type-check against the installed typescript, matching how `pnpm run build` already invokes it. Assisted-by: Claude-Code:GLM-5.2
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
1 participant
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.
Problem
CI's
pnpm/action-setup@v6step used a floatingversion: 11, which today resolved to the newly released pnpm 11.12.0. That release's self-installer crashes during its own headless install:This fails the frontend Lint job (and would fail any frontend-using workflow) before linting runs. It is not caused by the dependency bumps — the crash happens while pnpm installs itself from its own bundled lockfile.
Fix
Make
web/package.jsonthe single source of truth for the pnpm version:"packageManager": "pnpm@11.11.0"toweb/package.json.lint.ymlanddeploy-pages.yml, replace the floatingversion: 11withpackage_json_file: web/package.json, omittingversionsoaction-setup@v6reads the field (documented behavior).CI and local
corepacknow share one pinned version, so a bad future pnpm release can no longer break CI.Scope
main).CI/Run testsfailures — those are a separate issue: Dependabot bumped Jackson to2.22, which is not yet resolvable from Maven Central / scijava (Could not find artifact ...jackson-core:jar:2.22) alongside some checksum mismatches.Only
lint.ymlanddeploy-pages.ymlinstall pnpm (verified by grep across.github/workflows/).