@Xophmeister should I avoid manually updating flake.lock? #888

Seems there's compatibility issues: https://github.com/tweag/topiary/actions/runs/13704201091/job/38325408688?pr=896#step:9:618

should I avoid manually updating flake.lock? #888

It's fine to update it outside of the automation we now have 👍 In fact, it's probably necessary for the CI to run on this PR.

Seems there's compatibility issues: https://github.com/tweag/topiary/actions/runs/13704201091/job/38325408688?pr=896#step:9:618

Have the grammars changed between your version and this official version? I haven't looked into them, but that's the only thing I can think of (not that much has happened since your original OpenSCAD contribution was merged).

Have the grammars changed between your version and this official version? I haven't looked into them, but that's the only thing I can think of (not that much has happened since your original OpenSCAD contribution was merged).

Yes it looks like tree-sitter 0.25 was a breaking change in the ABI:
Release v0.25.0 · tree-sitter/tree-sitter

The internal ABI was bumped to 15. The main benefits this brings is that the language name, version, supertype info, and reserved words are added to the parsers. To use ABI 15, you must have a tree-sitter.json file in your repository, since the version information for the parser is pulled from this file.

Apologies: I messed up the merge conflict, so rebased and tried again... I will approve this, once the tests have passed 👍 but please double-check I haven't messed it up again, before you merge 😅

@Xophmeister everything LGTM!