-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
beta: revert #8640 - rustdoc versioning checks #9332
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
|
cc @CPerezz FYI. |
Fix semver docs for 1.51. 1.51 slightly changed the text of a few error messages. This should get CI passing again.
tests: Tolerate "exit status" in error messages "exit code" is wrong terminology on Unix. I am trying to fix this in Rust stdlib in rust-lang/rust#83462 but this currently breaks the cargo test suite. See that MR for full explanation of the change.
Thanks for the ping @ehuss. It's pretty unfortunate.. Anything I can help on? |
@CPerezz a less invasive version of #8640 would be to use |
I'm concerned that None of those are deal breakers on their own, but I'd like to consider other options if possible. |
@bors: r+ |
📌 Commit 6ce927a has been approved by |
☀️ Test successful - checks-actions |
[beta] Update cargo 2 commits in 90691f2bfe9a50291a98983b1ed2feab51d5ca55..d70308ef052397c7d16f881c2d973a8c5b4c23d9 2021-03-16 21:36:55 +0000 to 2021-04-06 17:32:27 +0000 - beta: revert rust-lang/cargo#8640 - rustdoc versioning checks (rust-lang/cargo#9332) - [beta] Fix publication of packages with metadata and resolver (rust-lang/cargo#9304)
#8640 has been causing some problems with rustbuild (see rust-lang/rust#83914 and rust-lang/rust#83530 (comment)). In order to give more time to figure out a solution, this reverts the change on beta. Will need to take some time to figure out what to do on master.
Also cherry picked the following to get tests passing: