Skip to content

Upgrade yarn to 4.18.0 - #90

Open
troberts-28 wants to merge 1 commit into
developfrom
chore/yarn-4.18
Open

troberts-28 wants to merge 1 commit into
developfrom
chore/yarn-4.18

Conversation

@troberts-28

Copy link
Copy Markdown
Owner

What

  • Upgrades yarn 4.12.0 to 4.18.0, and adopts two of the three supply-chain gates added since 4.13 rather than the opt-outs yarn set version writes by default.

Why

  • approvedGitRepositories: "**" is dropped because the lockfile has no git dependencies, so it would only pre-approve ones nobody has vetted.
  • npmMinimalAgeGate: 0 is dropped to take the 1-day default, quarantining newly published versions; a clean install still resolves with the gate active.
  • enableScripts: true is kept: four packages need build scripts, and simple-git-hooks installs the pre-commit hook from prepare.

Review Notes

  • Lockfile churn is 5 lines and no dependency resolutions change; the bulk of the diff is the vendored .yarn/releases binary swap.

`yarn set version` writes explicit opt-outs for the supply-chain gates
added between 4.13 and 4.18, so the upgrade preserves old behaviour rather
than adopting the new defaults. Two of those three are dropped here:

- approvedGitRepositories: "**" — removed. The lockfile has no git
  dependencies, so this only pre-approves ones nobody has vetted yet.
- npmMinimalAgeGate: 0 — removed, taking the 1-day default. Newly published
  versions are quarantined before they can be installed. Verified a clean
  install still resolves with the gate active.
- enableScripts: true — kept. Four packages need build scripts, and
  simple-git-hooks installs the pre-commit hook from `prepare`.

Lockfile churn is 5 lines; no dependency resolutions change.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014JJ2weaFu4jhu2XirMkbWe
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant