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 Dependencies & Bump to 1.11.0 #1355

Merged
merged 1 commit into from
Feb 14, 2018
Merged

Conversation

steffengy
Copy link
Contributor

@steffengy steffengy commented Feb 13, 2018

This makes proper architecture (=faster) windows builds available for 1.12.0.

I sneaked some version updates in to ensure that we're a step closer
to a consistent state on that front.

Some open points:

  • 1. Should we add a special case to self_update which
    makes the windows fixes available on 1.11.0 (this) already?
    e.g. hardcoding the version somewhere in the windows update logic introducted.
    This potentially could lead to infinite looping, if we're not careful.
  • 2. Any objections against the updates? Splitting them into a separate PR would be fine.
    (Not sure if CI even passes at this point, but we'll see)

r? @alexcrichton

This gets us atleast closer to not depending on winapi 0.2 anymore
and we use some more consistent package versions...
@alexcrichton
Copy link
Member

@bors: r+

Thanks! The updates look great to me and I think it's fine to hold off on the upgrades for another version

@bors
Copy link
Contributor

bors commented Feb 13, 2018

📌 Commit 745cf43 has been approved by alexcrichton

@bors
Copy link
Contributor

bors commented Feb 13, 2018

⌛ Testing commit 745cf43 with merge e751ff9...

bors added a commit that referenced this pull request Feb 13, 2018
Update Dependencies & Bump to 1.11.0

This makes proper architecture (=faster) windows builds available for **1.12.0**.

I sneaked some version updates in to ensure that we're a step closer
to a consistent state on that front.

Some open points:
- [ ] 1. Should we add a special case to self_update which
makes the windows fixes available on **1.11.0** (this) already?
e.g. hardcoding the version [somewhere](https://github.com/rust-lang-nursery/rustup.rs/blob/0068f0999acb923428cbd709650c57fbe04a0344/src/rustup-cli/self_update.rs#L1497) in the windows update logic introducted.
This potentially could lead to infinite looping, if we're not careful.
- [ ] 2. Any objections against the updates? Splitting them into a separate PR would be fine.
       (Not sure if CI even passes at this point, but we'll see)

r? @alexcrichton
@bors
Copy link
Contributor

bors commented Feb 14, 2018

☀️ Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing e751ff9 to master...

@bors bors merged commit 745cf43 into rust-lang:master Feb 14, 2018
@alexcrichton
Copy link
Member

Deployed!

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