Repository navigation
Fix playground CLI installation for 0.24.0 - #4
Merged
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.
The upstream sync pins the local Tree-sitter CLI to 0.26.3, which also matches the version requested by the playground exporter.
npm ci --ignore-scriptsleaves its native binary absent, sonpx --package=tree-sitter-cli@0.26.3selects the local wrapper and fails with ENOENT.Key Changes:
Touch Points:
.github/workflows/pages.ymlValidation: the exact base master
4178a059had a successful Pages run; the synchronized master56a91b4bfails specifically because the local CLI binary is missing. The same locked CLI rebuild succeeds in the parser CI on all three platforms. Pages deployment on the corrected master will be required before the 0.24.0 release.