You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I make a typo in the badges portion of my cargo library, there's no warning on compile nor on a dry-run publish, and I only get to see that something's wrong after the publish succeeds.
Try to catch publish errors using cargo publish --dry-run (no errors are displayed)
Publish the crate on crates.io using cargo publish (this displays a warning about is-it-mantained-issue-resolution being ignored as a badge)
Possible Solution(s)
I'd expect this should be possible by pinging the crates.io servers on a dry-run upload to check whether there are any invalid attributes. I expect cargo publish --dry-run to do everything that cargo publish does short of actually publishing it, so if there's a step separate from uploading that cargo publish does to display errors about ignored badges, maybe it could do that?
Notes
Output of cargo version: cargo 1.43.0-nightly (e57bd0299 2020-02-21)
The text was updated successfully, but these errors were encountered:
Problem
If I make a typo in the badges portion of my cargo library, there's no warning on compile nor on a dry-run publish, and I only get to see that something's wrong after the publish succeeds.
Steps
Cargo.toml
:cargo publish --dry-run
(no errors are displayed)cargo publish
(this displays a warning aboutis-it-mantained-issue-resolution
being ignored as a badge)Possible Solution(s)
I'd expect this should be possible by pinging the crates.io servers on a dry-run upload to check whether there are any invalid attributes. I expect
cargo publish --dry-run
to do everything thatcargo publish
does short of actually publishing it, so if there's a step separate from uploading thatcargo publish
does to display errors about ignored badges, maybe it could do that?Notes
Output of
cargo version
:cargo 1.43.0-nightly (e57bd0299 2020-02-21)
The text was updated successfully, but these errors were encountered: