Closed smheidrich closed 2 months ago
Thanks for the report and sorry for the inconvenience! I think you're right that pinning is probably the way to go. Unpinned versions made sense when there were weekly-ish changes going in so the consumers were regularly exercised by the CI, but since the grammar is basically feature-complete at this point we can assume changes will not come more regularly in the future.
Running the Python consumer example with a 0.23.* version of the tree-sitter Python package results in this exception:
This is due to a change mentioned in the 0.23.0 release notes:
It might make sense to pin the tree-sitter version (or version range) in the example's
requirements.txt
file to avoid similar issues going forward (but then you probably need something like Renovate to try and auto-update the version periodically).