-
-
Notifications
You must be signed in to change notification settings - Fork 118
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
Next release #235
Comments
Any updates on this? Especially since tokio 1.0 is out? |
I'll need to construct a Changelog first. Any help on this is welcomed help |
Can you please publish "0.7.0" release on crates.io as well. Thank you. |
There is an advisory out for the hyper version used by the 0.6.0 release: https://rustsec.org/advisories/RUSTSEC-2021-0020. The 0.7.0 release seems to fix this. |
On 08-02-2021 01:00:55, petreeftime wrote:
There is an advisory out for the hyper version used by the 0.6.0 release:
https://rustsec.org/advisories/RUSTSEC-2021-0020.
Maybe it is still a good idea to publish a 0.6.1 with a fixed hyper version (if
there is one).
|
I don't see a reason to not go directly to 0.7.0. AFAIK the changelog is complete and the API is sufficiently tested since a fair number of people follow the master to get access to tokio 1.0 and async-await (#230) |
On 08-02-2021 08:29:42, Eli W. Hunter wrote:
I don't see a reason to not go directly to 0.7.0.
Depends on the API changes, I am not up to date whether there are any.
If not, there's of course no reason to not update immediately.
If there are, users might want to continue using 0.6.x for a certain amount of
time.
But of course, as you said, most are tracking master anyways (so am I).
|
published 0.7.0. will be working on what would hopefully be a quick follow up after I work my way through the merge queue |
Is there a timeline for the next shiplift release? I'm keen to use both #229 and #220 in a released version.
The text was updated successfully, but these errors were encountered: