Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove explicit installation of tree-sitter CLI in CI check job #50

Closed

Conversation

bbannier
Copy link
Member

The GH action tree-sitter/setup-action/cli defaults to using the latest version of tree-sitter while we already already capture the tree-sitter version we build against in package.json. This duplication was not only unnecessary, but it also lead to version conflicts when checking whether generated files were up-to-date. This instead uses the tree-sitter CLI version as encoded for npm.

@bbannier bbannier self-assigned this Feb 21, 2025
@bbannier bbannier force-pushed the topic/bbannier/ci-consistent-tree-sitter-version branch 3 times, most recently from 28724ac to a95b225 Compare February 21, 2025 13:47
The GH action `tree-sitter/setup-action/cli` defaults to using the
latest version of tree-sitter while we already already capture the
tree-sitter version we build against in `package.json`. This duplication
was not only unnecessary, but it also lead to version conflicts when
checking whether generated files were up-to-date. This instead uses the
tree-sitter CLI version as encoded for npm.
@bbannier bbannier force-pushed the topic/bbannier/ci-consistent-tree-sitter-version branch from a95b225 to 5f91be1 Compare February 21, 2025 13:51
@bbannier bbannier closed this Feb 21, 2025
@bbannier bbannier deleted the topic/bbannier/ci-consistent-tree-sitter-version branch February 21, 2025 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant