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

Update futures preview 0.3.0-alpha.17 to 0.3.0-alpha.18 #1897

Closed
paulzhang5511 opened this issue Aug 12, 2019 · 4 comments
Closed

Update futures preview 0.3.0-alpha.17 to 0.3.0-alpha.18 #1897

paulzhang5511 opened this issue Aug 12, 2019 · 4 comments
Labels
E-easy Effort: easy. A task that would be a great starting point for a new contributor.

Comments

@paulzhang5511
Copy link

The futures-rs 0.3.0-alpha.18 is released. futures-preview

@seanmonstar seanmonstar added E-easy Effort: easy. A task that would be a great starting point for a new contributor. B-upstream Blocked: needs a change in a dependency or the compiler. labels Aug 14, 2019
@seanmonstar
Copy link
Member

This is blocked on tokio upgrading.

@mrjoe7
Copy link

mrjoe7 commented Aug 19, 2019

Tokio 0.2.0-alpha.2 is now using futures-rs 0.3.0-alpha.18

@seanmonstar seanmonstar removed the B-upstream Blocked: needs a change in a dependency or the compiler. label Aug 19, 2019
@DoumanAsh
Copy link
Contributor

Is there actual need to bump version? cargo update should pick up latest automatically

@Nemo157
Copy link

Nemo157 commented Aug 20, 2019

@DoumanAsh during these alphas there is no guarantee of semver compatibility, so crates that are willing to track the unstable edge should all be aggressively bumping their versions up to the latest release to provide the highest chance of interoperability.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E-easy Effort: easy. A task that would be a great starting point for a new contributor.
Projects
None yet
Development

No branches or pull requests

5 participants