Bump TreeSitter version to 0.25.6
#401
Closed
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
There was a problem hiding this comment.
Pull Request Overview
This PR bumps the tree-sitter dependency version from 0.20.9 to 0.25.6 to resolve version mismatch issues with CodeEditSourceEditor.
- Update tree-sitter dependency version
- Aims to streamline dependency compatibility in Xcode-managed Swift projects
Author
|
Nevermind, just realized how deep of a rabbit hole this is 🥲 |
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.
Thank you for building this amazing library!
I'm using an abstraction over Runestone on iOS and visionOS and CodeEditSourceEditor on macOS on my app. CodeEditSourceEditor recently bumped their tree-sitter version to the latest release, causing dependency version mismatch headaches when using it together with Runestone in the same Xcode-managed Swift project. So the easiest way for me to fix my problem that didn't involve breaking things out into a separate package was to just bump Runestone's tree-sitter dependency, too.
Please let me know if this doesn't make sense to you to upstream at the moment and I'll keep it downstream. 🙂