ci(typescript): use workspace-local pnpm tooling - #2178
Merged
Conversation
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
Preserves the intentional TypeScript tooling work from #2161 as an independent change. TypeScript CI, pre-commit, and auto-fix now use the workspace-owned pnpm commands, and typechecking builds
@trycua/corebefore dependent packages.Changes
libs/typescript/package.jsonin TypeScript CItypecheck,format, andformat:checkcommandsValidation
pnpm@10.12.3 -C libs/typescript install --frozen-lockfilepnpm@10.12.3 -C libs/typescript typecheckpnpm@10.12.3 -C libs/typescript format:checkThe host pnpm 11 policy rejected the existing lockfile because of its configured minimum package age; validation therefore used the workspace-declared pnpm 10.12.3 without changing the lockfile or policy.
Sidecar B from the #2161 second-wave landing plan. It is independent of the CUA Driver stack.