Bump to version 20 of tree-sitter

[VixieTSQ]

I tried to do this myself but this repo is different most tree-sitter repos as it really has 2 parsers. I couldn't figure out how exactly this should work in the bindings.

[314eter]

I updated tree-sitter and did a rebuild.

@maxbrunsfeld Can you release a new version on NPM and crates.io?

[VixieTSQ]

I updated tree-sitter and did a rebuild.

@314eter The rust binding still depends on tree-sitter 0.19 in cargo.toml.

[314eter]

Fixed in #58.

[torhovland]

This still needs a release.

[314eter]

@maxbrunsfeld Can you create a new release?

[aryx]

I've created a new release: https://github.com/tree-sitter/tree-sitter-ocaml/releases/tag/v0.20.0

[aryx]

Can we close the issue?

[314eter]

@aryx I created a new release with the latest changes. Do you have access to the tree-sitter organization on crates.io and NPM to publish the new version there? I can only create releases on Github.

[aryx]

I think we could add an action like they did for tree-sitter-java. See this thread: https://github.com/tree-sitter/tree-sitter-java/pull/98

[314eter]

That looks like a good solution for crates.io. It would be nice to have something similar for NPM. I see https://www.npmjs.com/package/tree-sitter-java is still on 0.19.1 too.

[VixieTSQ]

Should this issue still be open? It looks like the issue is, is that the new changes weren't pushed to crates.io? Am I correct in that?

[314eter]

I'll close this one and create a new issue to implement the publish action.