chore: unify pnpm version and mark non-publishable manifests private - #1067
Open
abhithesys wants to merge 2 commits into
Open
chore: unify pnpm version and mark non-publishable manifests private#1067abhithesys wants to merge 2 commits into
abhithesys wants to merge 2 commits into
Conversation
- Pin pnpm via root packageManager field (10.33.0); all workflows now use versionless pnpm/action-setup@v6 that reads it (previously 9.0.6 / 9.15.4 / 10.33.0 across workflows). The matrix-driven pnpm setup in cli-e2e keeps its per-matrix version by design. - Mark root package.json private (not a real package; guards against accidental recursive publish). - Mark examples/harnesses/vercel-eve private (only non-private manifest inside the workspace globs; publish-leak risk). Prerequisite for changesets-based release automation. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Prerequisite hygiene for the changesets-based release automation in the next PR. No behavior change to any published package.
"packageManager": "pnpm@10.33.0"to the root manifest; all workflows now use versionlesspnpm/action-setup@v6, which reads that field. Previously four workflows pinned four different versions (9.0.6, 9.15.4, 10.33.0, unpinned) — and 9.0.6 predates pnpm catalogs, whichpnpm-workspace.yamluses. The matrix-driven pnpm setup incli-e2e.ymlkeeps its per-matrix version by design (it tests template compat across package managers).package.json→private: true. It's not a real package (name: "OpenUI", version: 1.0.1); this guards against any recursive publish ever pushing it to npm.examples/harnesses/vercel-eve→private: true. It was the only non-private manifest inside the workspace globs — a publish-leak risk once tooling iterates the workspace.Verified: lockfile version is unchanged, and the newer workflows already ran this workspace on 10.33.0.