update crate dependencies

[steveklabnik]

I wanted to update mdbook's version. This ended up updating a bunch of other stuff too.

I am not sure if updating this much stuff is considered a Good Idea or not; happy to figure out how to make it smaller if someone can help me figure out how to use x.py to do it.

[rust-highfive]

r? @alexcrichton

(rust_highfive has picked a reviewer for you, use r? to override)

[Mark-Simulacrum]

Will leave for @alexcrichton to sign off on but looks good in general to me.

[est31]

if someone can help me figure out how to use x.py to do it.

I personally don't have any problems with updating all dependencies (this should be done from time to time either way IMO), but if you want to update only one crate, cd'ing into the src directory and then doing cargo update -p mdbook should do it

[alexcrichton]

@bors: r+

[bors]

📌 Commit ec22738 has been approved by alexcrichton

[ishitatsuyuki]

I feel that Cargo.lock updates should have priority; otherwise it would easily conflict with other changes which have more risk to fail.

[Mark-Simulacrum]

Not sure what you mean. We try to avoid updates in non-dedicated pull requests to Cargo.lock, so conflicts should be rare.

[ishitatsuyuki]

I mean, this will virtually block another approved PR from being merged as it would conflict as soon as this is merged. To minimize the cycle time, this PR should be prioritized.

[Mark-Simulacrum]

I wouldn't expect there to be conflicts unless the other PR also updated Cargo.lock; unless I'm missing something, that's rare -- and not all that harmful.

Also, if we wait till the queue is mostly empty, this PR will have less of an effect then (so again, prioritizing it seems odd).

[est31]

I mean, this will virtually block another approved PR from being merged as it would conflict as soon as this is merged.

A PR which this blocks would have to update Cargo.lock, which happens very rarely.

[frewsxcv]

@bors rollup

[bors]

☔ The latest upstream changes (presumably #42995) made this pull request unmergeable. Please resolve the merge conflicts.

[bors]

🔒 Merge conflict

[aidanhs]

Hi @steveklabnik looks like this has some merge conflicts.

[steveklabnik]

Updated; looks like it's good to go now.

[alexcrichton]

@bors: r+

[bors]

📌 Commit 4d14d75 has been approved by alexcrichton

[bors]

🔒 Merge conflict

[ishitatsuyuki]

Maybe it's time to develop a custom merge driver (that clear and generates lockfile on every merge conflict).

[bors]

☔ The latest upstream changes (presumably #43115) made this pull request unmergeable. Please resolve the merge conflicts.

[arielb1]

Hey @steveklabnik - looks like this just needs a rebase. Friendly ping to make sure it isn't getting lost.

[steveklabnik]

#42936 (comment)

@bors: r=alexcrichton p=1

giving this a priority because i'm sick of rebasing it and want to make sure it lands before next week

[bors]

📌 Commit 4871dba has been approved by alexcrichton

[steveklabnik]

@bors: rollup-

[bors]

⌛ Testing commit 4871dba with merge d1f1f86...

[bors]

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