Upgrade core foundation
<!-- Please describe your changes on the following line: -->
This PR is the final one in a chain of PRs that tries to make a breaking change to `core-foundation`. This PR makes sure Servo only use the new, not yet released `core-foundation 0.5.0`. The changes in `core-foundation` and why it is not yet published can be read in the comments on this PR: servo/core-foundation-rs#132
Basically we want all of Servo (and deps) to be ready for a fairly swift upgrade from `core-foundation` `0.4.6` to `0.5.0` once it's released, so we don't end up in some state where we depend on, and have to maintain both, for an extended period of time.
This PR is **not ready for merge** in its current state. The following must be done first:
- [x] Merge servo/core-foundation-rs#132 and publish.
- [x] Merge servo/core-graphics-rs#110 and publish.
- [x] Merge servo/core-text-rs#75 and publish.
- [x] Merge servo/cocoa-rs#181 and publish.
- [x] Merge servo/glutin#142 and publish.
- [x] Merge servo/io-surface-rs#60 and publish.
- [x] Merge servo/skia#148.
- [x] Merge servo/rust-azure#282.
- [x] Merge servo/webrender#2299.
- [x] Merge servo/surfman#118 and publish.
- [x] Remove the commit in this PR that temporarily adds patch entries to `Cargo.toml`.
- [x] Update Cargo.lock again to not point to my feature branches.
For some of the dependencies I might accidentally have bumped the version as if it was a breaking change when it in fact wasn't. It was a bit messy to figure out all the details in so many and large crates. But hopefully I did not do the inverse, only bump the patch version where the change actually broke something.
Ping @jdm and @nox who have been the ones commenting on the initial PR.
---
<!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: -->
- [X] `./mach build -d` does not report any errors
- [X] `./mach test-tidy` does not report any errors
<!-- Either: -->
- [X] These changes do not require tests because they don't change any code, just upgrade dependencies.
<!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.-->
<!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/19759)
<!-- Reviewable:end -->
faern commentedJan 13, 2018
•
edited
This PR is the final one in a chain of PRs that tries to make a breaking change to
core-foundation. This PR makes sure Servo only use the new, not yet releasedcore-foundation 0.5.0. The changes incore-foundationand why it is not yet published can be read in the comments on this PR: servo/core-foundation-rs#132Basically we want all of Servo (and deps) to be ready for a fairly swift upgrade from
core-foundation0.4.6to0.5.0once it's released, so we don't end up in some state where we depend on, and have to maintain both, for an extended period of time.This PR is not ready for merge in its current state. The following must be done first:
Cargo.toml.For some of the dependencies I might accidentally have bumped the version as if it was a breaking change when it in fact wasn't. It was a bit messy to figure out all the details in so many and large crates. But hopefully I did not do the inverse, only bump the patch version where the change actually broke something.
Ping @jdm and @nox who have been the ones commenting on the initial PR.
./mach build -ddoes not report any errors./mach test-tidydoes not report any errorsThis change is