Repository navigation
wreq: Add versions 0.12.2, 0.12.3, 0.13.0 - #2677
Draft
riseproject-dev[bot] wants to merge 3 commits into
Draft
riseproject-dev[bot] wants to merge 3 commits into
riseproject-dev[bot] wants to merge 3 commits into
Conversation
Contributor
|
Signed-off-by: riseproject-dev[bot] <330740410+riseproject-dev[bot]@users.noreply.github.com>
riseproject-dev
Bot
force-pushed
the
github-actions/nightly-upgrade/wreq
branch
from
October 6, 2026 08:46
9ca3024 to
2ed9b6c
Compare
Starting at 0.12.2, wreq-python's own Cargo.toml [patch.crates-io] pins wreq/wreq-util/btls to exact git revs directly, replacing the floating crates.io `wreq = "6.0.0-rc"` requirement 0.12.1 still has. Our CIBW_BEFORE_BUILD_LINUX unconditionally ran `cargo update -p wreq --precise 6.0.0-rc.29` for every version, which cargo reads as a git ref against a git-patched dependency -- '6.0.0-rc.29' isn't one in 0x676e67/wreq, so every 0.12.2+ build failed at 'revspec 6.0.0-rc.29 not found'. Kept version-conditional so a rebuild of the already-published 0.12.1 still gets its pin.
0.13.0 adds netty = { git = "...netty", branch = "main" } to wreq-python's
own [patch.crates-io], and netty's Cargo.toml separately patches http2 to a
specific git rev for a Connection::extended_connect_protocol method no
http2 release has yet ("Remove once an http2 release includes" it, per
netty's own comment) — but Cargo only honours a dependency's [patch] table
for the top-level workspace, so wreq-python's build resolves crates.io's
http2 instead and fails:
error[E0599]: no method named `extended_connect_protocol` found for
struct `http2::client::Connection<T, B>`
Add the same patch to wreq-python's own Cargo.toml before locking, version-
scoped to 0.13.0 since 0.12.1/0.12.2/0.12.3 have no netty dependency at all.
This branch has not been deployed
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.
Automatically generated by the nightly
check_versions.pyrun.wreq v0.12.1 -> v0.12.2, v0.12.3, v0.13.0
Every
- version:entry added todocs/packages/wreq.yamlis built by this PR's ownbuild-wreq.ymlrun; merging publishes the wheels.