Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 0.12.0 ? #171

Closed
midnightexigent opened this issue Nov 18, 2021 · 3 comments
Closed

Release 0.12.0 ? #171

midnightexigent opened this issue Nov 18, 2021 · 3 comments

Comments

@midnightexigent
Copy link

Latest version on crates.io is 0.11.2

@calebcartwright
Copy link
Member

calebcartwright commented Nov 24, 2021

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-
Copy link

Qix- commented Aug 26, 2022

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
Copy link
Member

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants