-
Notifications
You must be signed in to change notification settings - Fork 342
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 1.13.0? #1081
Comments
Is this project even still active? It hasn't been published in two years, which is a little disheartening. |
There is still commits every few months being merged to Best we can do is wait until one of the maintainers is willing to tackle putting out a new release. There can be some friction to doing that, especially with such a long gap since the last one, but if that's a concern perhaps they could express what needs to be done that a contributor could help push forward. A friendly ping to recently active maintainers on the project may get some attention if you're lucky. @dignifiedquire @Keruspe @Fishrock123 Only one of those maintainers pinged has frequent Github activity, they've likely got quite a lot going on. The other two are less likely to notice / respond to the ping from the lack of activity though 😅 |
Let's see how #1083 goes |
Well, at least #1036 (comment) will need addressing first |
I've now submitted #1084 to address #1036 (comment). |
I've fixed a few follow-up problems, CI is now green |
#1083 is preparing the release, but it hasnt happened yet. |
Ah, haven't created it on GitHub indeed, but it's on crates.io |
1.12.0 was released in June 2022, it's been over 2 years.
This issue is tracking crates with
async-std
as one blocker waiting on a release for aasync-std
PR that was merged back in May 2023.The text was updated successfully, but these errors were encountered: