Update the tree-sitter-nix crate in crates.io

[k3yss]

A lot of PR's have been merged since v0.0.1, we should consider releasing the next version v0.0.2

cc https://docs.rs/tree-sitter-nix/0.0.1/tree_sitter_nix/

[k3yss]

Tagging @adisbladis as this issue (#47) mentions they might be the current maintainer. Apologies if the ping caused any inconvenience

[adisbladis]

Tagging @adisbladis as this issue (#47)

Just for some clarity, I'm not the maintainer, just a maintainer.
I don't have access to the package on crates.io, only @cstrahan has.

@cstrahan: If you could give me access I could set up some automation that publishes the package.

[zimbatm]

ping!

[patrickt]

Hey there 👋🏻 A release here would be welcome, as we at GitHub use this crate for syntax highlighting and prefer to use released crates for reliability and auditing’s sake.

[funkeleinhorn]

Could we tag the commit 02878b40ac77d2889833519c6b6e9e63cfc690e6 as v0.0.1 to have an easier mapping between source and release as this commit should be the version currently released on crates.io. Can someone confirm this? Also https://crates.io/crates/tree-sitter-nix lists @zimbatm and @cstrahan as the crates.io owners. Do you @zimbatm have access to the tree-sitter-nix crate and could do a new release as @cstrahan seems to be unresponsive? If we have lost access to the tree-sitter-nix crate I would suggest to republish this project as a new crate e.g. tree-sitter-nix-ng or so to regain access to crates.io. In any case we should start tagging releases in git and set up some automation to auto publish the tags to crates.io and give more maintainers access to crates.io to prevent situations like this in the future. What are your thoughts on this?

[zimbatm]

Done. Both releases are now tagged and published to crates.io.

@funkeleinhorn if you want to submit a PR for automating the release process, I'd be happy to get it merged.

[funkeleinhorn]

Done. Both releases are now tagged and published to crates.io.

@funkeleinhorn if you want to submit a PR for automating the release process, I'd be happy to get it merged.

I have opened a PR to add a release automation #128 Please have a look and suggest improvements. I just picked one of the first good looking suggestions on the internet to have something to build upon ;)