deps: pnpm to v11.12.0

[dejanvasic85]

This PR contains the following updates:

Package	Type	Update	Change
pnpm (source)	packageManager	minor	11.11.0 → 11.12.0
pnpm (source)	uses-with	minor	11.11.0 → 11.12.0

---

Release Notes

pnpm/pnpm (pnpm)

v11.12.0

Compare Source

Minor Changes

• a897ef7: Custom fetchers exported from a pnpmfile can now delegate by returning a { delegate: <resolution> } envelope: pnpm rewrites the package's resolution to the delegated shape and runs the built-in fetcher on it. This is the portable delegation form that also works in pacquet, where cafs and fetchers cannot be passed to the hook. Related to pnpm/pnpm#11685.

Patch Changes

• 2b02764: The changed-packages filter (--filter "...[<since>]") no longer allows an option-like <since> value (such as --output=<path>) to be interpreted as a git option — git now rejects it as a bad revision. The repository root is also resolved to the nearest .git entry, so the filter works in a git worktree checked out inside another repository's tree.

• 43711ce: pnpm outdated no longer checks the registry for dependencies that are resolved from local link:, file:, or workspace: references in the lockfile #​12827.

• 3c6718b: Fixed a deadlock in peer dependency resolution: pnpm install hung forever when a peer dependency cycle spanned a project's own dependencies and auto-installed peer providers, for example when installing electron-builder@26.15.3 #​12921.

• 252f15e: Fixed peer dependency auto-install picking a version the peer range rejects. In a workspace with several projects, a package declaring a peer dependency with a semver range (for example ^1.0.0) could get the highest version found anywhere in the workspace (for example a 2.0.0 resolved for another project) instead of a version that satisfies the range. Peers are now deduplicated onto the highest preferred version that satisfies the declared range, and when none does, the range is resolved from the registry.

  Also fixed re-resolving with an existing lockfile hoisting a different peer version than a fresh install of the same manifest: root dependencies reused from the lockfile were invisible to peer hoisting, so a peer that a root dependency provides could be bound to another version.

• a38adda: pnpm self-update <version> now installs the requested pnpm version when it matches the currently running version but is missing from the global self-update directory.

• 6a85968: pnpm stage list now stops paginating after a fail-safe cap of 1000 pages, so a misbehaving registry cannot keep the command looping forever.

• eee7c9a: verify-deps-before-run no longer spawns a pnpm install when pnpm is executed in a directory that has no package.json. A mistyped command run outside a project (for example pnpm witch 10 login) used to crash with a confusing error from the spawned install; now it fails with the regular "no package.json found" error.

---

Configuration

📅 Schedule: (in timezone Australia/Melbourne)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

Summary by CodeRabbit

• Chores
  • Updated the project’s package manager tooling to pnpm 11.12.0.
  • Standardized automated testing, crawling, and deployment workflows on the updated tooling version.
  • No user-facing functionality changes.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
williamstownsc	Ready	Preview, Comment	Jul 13, 2026 6:49am

[coderabbitai]

Warning

Review limit reached

@dejanvasic85, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 32 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: cd63ee0c-c661-4698-b871-3462658f055c

📥 Commits

Reviewing files that changed from the base of the PR and between 87be238 and 8006313.

📒 Files selected for processing (3)

• .github/workflows/ci.yml
• .github/workflows/crawl.yml
• .github/workflows/deploy-sanity.yml

📝 Walkthrough

Walkthrough

Updates Node.js and pnpm from 11.11.0 to 11.12.0 across GitHub Actions workflows and package.json.

Changes

Tooling version alignment

Layer / File(s)	Summary
Workflow and package tooling updates .github/workflows/ci.yml, .github/workflows/crawl.yml, .github/workflows/deploy-sanity.yml, package.json	GitHub Actions mise configurations and the packageManager field now reference version 11.12.0.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• dejanvasic85/williamstownsc#684: Previously updated the same workflows and package metadata to adjacent Node.js and pnpm versions.
• dejanvasic85/williamstownsc#721: Updated the same CI tooling versions from 11.10.0 to 11.11.0.
• dejanvasic85/williamstownsc#468: Migrated the same workflows to jdx/mise-action.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely summarizes the main change: upgrading pnpm to v11.12.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch renovate/all-minor-patch

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[dejanvasic85]

Closing — pnpm 11.12.0 has a confirmed upstream bug that breaks pnpm/action-setup self-install (Cannot use 'in' operator to search for 'integrity' in undefined, createFullPkgId). See pnpm/action-setup#276. standalone: true doesn't help (binary exits 127).

Staying on 11.11.0 until pnpm ships a fix. #731 adds a Renovate rule pinning pnpm to <11.12.0 so this upgrade won't be re-raised until then.