Christian Clason

We don't tie parser versions to the tree-sitter crate (that's what ABI is for, which can be checked independently of the version). And aren't the bindings autogenerated?

The versioning scheme is basically semver, from the point of view of queries (so reflecting minor/major/breaking changes in the grammar _only_). And try removing the bindings first; some files are...

Actually, versioning and publishing should be handled by our workflows; we'd prefer it if there was no "rogue publishing" that can interfere with that. @ObserverOfTime

Ideally they should be available org-wide, like the NPM token (as we eventually want to publish ALL THE PARSERS).

@ObserverOfTime Can you set up the token and the publish workflow for this repo then?

Can we use our github app? It's a bit annoying that we have to tie packages to personal accounts that may move on, orphaning the package.