-
Notifications
You must be signed in to change notification settings - Fork 875
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
Can we get a new version pushed to crates.io please? #2273
Comments
Happy to cut a new release, though My plan thus far was to wait for #2248 to merge and then cut a release candidate and later on a full release. Why a release candidate first? (1) it is a pretty large release and (2) #2248 is a large change literally at the core ( Would that work for you @gilescope? Does the above issue currently block you in any way? |
I'm sure those timescales will be fine. At some point there might need to be another one when I finally get rand upgraded (but that's not likely to be a quick thing). |
I just published a release candidate (see #2290 (comment)). Giving some time for people to test the release candidate. In case nothing comes up, I will cut a new release. |
Closing here since |
The latest code doesn't depend on the deprecated https://crates.io/crates/cpuid-bool/0.1.2 crate any more (thanks to soketto 0.7 upgrading their sha-1 crate).
The text was updated successfully, but these errors were encountered: