Repository navigation
fix(release): send a user agent in the crates.io lookup - #190
Merged
Merged
Conversation
crates.io now answers a request without a user agent with HTTP 403. The publish helper then stopped before cargo publish, so the v0.4.0 release run published no crate. Signed-off-by: Bart Waardenburg <bart@waardenburg.dev>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
crates.io answers a request without a user agent with HTTP 403. The publish helper then stopped before
cargo publish, so the v0.4.0 release run published no crate. The npm packages published.The lookup now sends a user agent. A new test checks the
curlarguments. After the merge, arelease.ymldispatch frommainpublishes the 0.4.0 crates. The npm step skips the versions that npm already has.