chore: bump pnpm to 11.22.0 - #5339
Merged
Merged
Conversation
🦋 Changeset detectedLatest commit: 255ed6a The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
github-actions
Bot
added
👨🏻🍳 cookbooks
🚧 chore
odinr
force-pushed
the
chore/bump-pnpm-11.22.0
branch
from
August 19, 2026 15:38
472477b to
384f418
Compare
- packageManager: pnpm@10.20.0 -> 11.22.0 - move overrides/patchedDependencies from package.json's now-inert "pnpm" field into pnpm-workspace.yaml (pnpm 11 only reads settings from there) - add minimumReleaseAgeExclude for @changesets/cli and @changesets/write: both were published <24h ago (pnpm 11's new default 24h supply-chain policy blocked the lockfile), but are already-vetted devDependency-only build tooling from the changesets v2->v3 migration (PR #5337) - pnpm-lock.yaml churn is from autoInstallPeers defaulting to true in pnpm 11 (resolves previously-unmet optional peers); no dependency version changes - fix biome.json's $schema version notice (2.5.6 -> 2.5.8, matching the installed Biome version) Also migrate cookbooks/portal-analytics off the deprecated, no-longer- supported @equinor/fusion-react-progress-indicator: EquinorLoader now uses EDS's Progress.Star (already a workspace dependency) with a visible Typography caption plus an aria-label on the spinner. Verified: full biome check, fusion-lint, affected build (81/81, excluding the pre-existing, unrelated cli-plugin-copilot failure already on main pending a separate fix), and test suite (86/86 files, 825/825 tests) all pass.
odinr
force-pushed
the
chore/bump-pnpm-11.22.0
branch
from
August 19, 2026 15:42
384f418 to
c081a74
Compare
onlyBuiltDependencies (and neverBuiltDependencies/ignoredBuiltDependencies/ ignoreDepScripts) were removed in pnpm v11, replaced by the allowBuilds boolean map. pnpm auto-wrote a placeholder entry for @parcel/watcher during local `pnpm approve-builds` that needed a real true/false value. Without this, CI's frozen install hard-fails (strictDepBuilds defaults to true in v11) on any build script pnpm hasn't seen approval for.
Contributor
Coverage Report
File CoverageNo changed files found. |
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.
Summary
packageManagerfrompnpm@10.20.0topnpm@11.22.0.overrides/patchedDependenciesfrompackage.json's now-inert"pnpm"field intopnpm-workspace.yaml— pnpm 11 only reads settings frompnpm-workspace.yaml, notpackage.json.minimumReleaseAgeExcludefor@changesets/cliand@changesets/write: both were published <24h ago, tripping pnpm 11's new default 24h supply-chain policy on the existing lockfile. Both are already-vetted devDependency-only build tooling from the changesets v2→v3 migration (chore: migrate changesets tooling v2 -> v3 #5337).pnpm-lock.yamlchurn is fromautoInstallPeersdefaulting totruein pnpm 11 (resolves previously-unmet optional peers likecss-to-react-native,fsevents) — no actual dependency version changes.biome.json's$schemaversion notice (2.5.6 → 2.5.8, matching the installed Biome version).Also included: migrate
cookbooks/portal-analyticsoff the deprecated, no-longer-supported@equinor/fusion-react-progress-indicator.EquinorLoadernow uses EDS'sProgress.Star(already a workspace dependency) with a visibleTypographycaption plus anaria-labelon the spinner for accessibility parity.Validation
pnpm exec biome check— cleanpnpm lint:fusion— clean for touched packages/cookbooks (2 pre-existing warnings onmain, unrelated to this diff, left untouched)pnpm turbo run build --affected— 81/81 passing (excludes@equinor/fusion-framework-cli-plugin-copilot, which fails onmaintoday for an unrelated reason pending a separate fix)pnpm test run— 86/86 test files, 825/825 tests passingChangeset
.changeset/portal-analytics_migrate-progress-indicator.md(patch bump forportal-analytics)