chore: migrate to pnpm 11 + add minimumReleaseAge#116
Merged
Conversation
Bump packageManager from pnpm@8.6.5 to pnpm@11.1.3 (lockfile v6 -> v9). Add minimumReleaseAge: 2880 (48h delay before installing newly published packages) with @vercel/* excluded so workspace and first-party releases install immediately. Add allowBuilds allowlist for the five packages with lifecycle scripts under pnpm v10+ strict policy. Move the valibot override out of package.json (pnpm 11 reads it from pnpm-workspace.yaml). Mirrors vercel/analytics#202. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The override was added in #104 as a guardrail when Nuxt support landed, but @remix-run/dev (the only transitive consumer) now resolves valibot@1.4.0 on its own — the override is a no-op. Removing it also fixes Vercel deploys, which run pnpm 9 (reads overrides from package.json, not pnpm-workspace.yaml) and were failing with LOCKFILE_CONFIG_MISMATCH. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The lockfile regen during the pnpm 11 migration let biome float from 2.3.10 to 2.4.15 via the existing caret range, and 2.4.x introduced stricter assist and lint rules (organizeImports for exports, useHookAtTopLevel triggering on Vue's setup()) that broke CI on pre-existing code unrelated to this PR. Pin to the exact version that main was using to keep this PR scoped to pnpm. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
dferber90
approved these changes
May 21, 2026
luismeyer
approved these changes
May 21, 2026
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
3 participants
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.
📓 What's in there?
Mirrors vercel/analytics#202 in this repo:
packageManagerfrompnpm@8.6.5→pnpm@11.1.3(lockfile v6 → v9, fully regenerated).minimumReleaseAge: 2880(48-hour quarantine before installing newly published versions of transitive deps) withminimumReleaseAgeExclude: ['@vercel/*']so workspace/first-party releases install immediately. This is the main motivation — a defense-in-depth measure against malicious or accidentally broken package releases.allowBuildsallowlist for the five packages in this repo that have lifecycle scripts (@parcel/watcher,@swc/core,esbuild,lefthook,sharp). Required since pnpm v10+ blocks them by default.valibotoverride frompackage.json→pnpm-workspace.yaml(pnpm 11 no longer reads thepnpm.*block inpackage.json).🧪 How to test?
corepack pnpm installfrom a clean clonecorepack pnpm -r --filter @vercel/speed-insights build🤖 Generated with Claude Code