Skip to content

chore(cargo): Update url crate to 0.5 #685

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

Merged
merged 1 commit into from
Nov 23, 2015
Merged

Conversation

untitaker
Copy link
Contributor

A recent update in url triggered a version split in my application and
broke my build.

Since hyper is still compatible with 0.2, I think it might make sense to
still allow that version.

@untitaker
Copy link
Contributor Author

Build failure doesn't seem to be related. I'm not sure.

@untitaker
Copy link
Contributor Author

Perhaps wait for servo/rust-url#138

@untitaker untitaker changed the title chore(cargo): Update url crate to 0.4 chore(cargo): Update url crate to 0.5 Nov 22, 2015
@untitaker
Copy link
Contributor Author

This is now review-ready, turns out pinning only by version-range is a bad idea.

Anyone?

@Ryman
Copy link
Contributor

Ryman commented Nov 22, 2015

@untitaker for my own reference, what went wrong with a version range?

reem added a commit that referenced this pull request Nov 23, 2015
chore(cargo): Update url crate to 0.5
@reem reem merged commit b4a9227 into hyperium:master Nov 23, 2015
@untitaker
Copy link
Contributor Author

@Ryman Just problems in principle: You might expose different behavior depending on which url version is installed. Some of that behavior differences are catched by the typesystem and the resulting combination just doesn't compile, but others may be more subtle.

@untitaker untitaker deleted the url-update branch November 23, 2015 14:11
@untitaker
Copy link
Contributor Author

BTW: You'd probably have to bump the minor version after this, since url is part of your public API

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

Successfully merging this pull request may close these issues.

3 participants