Repository navigation
Fix pnpm workspace change detection in VS Code publish workflow - W-24490676 - #195
Merged
Merged
Conversation
mshanemc
approved these changes
Oct 12, 2026
2 tasks
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
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
Install the VS Code change-detector tools in a temporary directory outside the consumer repository. Run
tsxfrom that directory while keeping the consumer checkout as the working directory.The current
npm install --no-saveruns inside pnpm workspaces and fails onworkspace:*dependencies before change detection starts. This affected the Apex LS nightly release. The change leaves npm, Yarn, and pnpm caller inputs unchanged.Validation
git diff --check.Work item: W-24490676
Related Apex LS PR: forcedotcom/apex-language-support#746