Release 0.12.0 ?

[midnightexigent]

Latest version on crates.io is 0.11.2

[calebcartwright]

Thanks for reaching out. This has been discussed a few times in various places that probably aren't immediately obvious, so while I'm going to close this issue as not actionable (currently) I will use it as a channel to communicate why we can't publish 0.12.0 (yet) and pin the issue accordingly for visibility.

In short, we were experimenting with various things that have been merged in source but which also would break compatibility with earlier versions of rusty-hook (refs #129). While we're certainly still in beta/pre-release mode, we take backwards compatibility very seriously and don't want to disrupt anyone that's currently using rusty-hook in the v0.x stages.

Folks should never try to install rusty-hook from source because part of its operations is predicated on fixed release points/versions which come from crates.io. Installing from source control is unsupported and will (sooner or later) create the potential for breakage. This will probably continue to be the case unless/until cargo support for bindeps is stabilized (RFC 3028)

So for now folks should continue to leverage the released 0.11.2 version from crates and subscribe to this issue for updates on the next release

[Qix-]

Sorry to bump, but... it's coming up on a year since the last release and the arrays feature would be really, really nice to have. Any chance of a release? If something is breaking a 1.0 would be cool too I would imagine :)

Thanks for a great package :)

[calebcartwright]

Unfortunately I remain pressed for time and spread a little too thin. Cutting a release is something I could take care of pretty easily, but I'm not sure when I'd personally be able to carve out enough bandwidth to address the aforementioned compatibility issues. If someone wants to try to pick that up again it would be great.

Thanks for the kind words though!

[xamgore]

@calebcartwright rusty-hook 0.11 is an amazing piece of software. Still, it is incomplete as there is no way to pass arguments from git to the hook scripts. Thus, you can't define commit-msg and prepare-commit-msg, as well as prevent post-push from being called on remote branch deletion.

Is it possible to release 0.12 after 3 years passed? The desired backward compatibility is not so important, as each 0.y release is considered major, after all.