Skip to content

wreq: Add versions 0.12.2, 0.12.3, 0.13.0 - #2677

Open
riseproject-dev[bot] wants to merge 3 commits into
mainfrom
github-actions/nightly-upgrade/wreq
Open

riseproject-dev[bot] wants to merge 3 commits into
mainfrom
github-actions/nightly-upgrade/wreq

Conversation

@riseproject-dev

@riseproject-dev riseproject-dev Bot commented Oct 3, 2026 •

Copy link
Copy Markdown
Contributor

Automatically generated by the nightly check_versions.py run.

wreq v0.12.1 -> v0.12.2, v0.12.3, v0.13.0

Every - version: entry added to docs/packages/wreq.yaml is built by this PR's own build-wreq.yml run; merging publishes the wheels.

@riseproject-dev
riseproject-dev Bot requested a review from luhenry October 3, 2026 07:46
@github-actions

github-actions Bot commented Oct 3, 2026 •

Copy link
Copy Markdown
Contributor
PR Preview Action v1.8.1

QR code for preview link

🚀 View preview at
https://riseproject-dev.github.io/python-wheels/pr-preview/pr-2677/

Built to branch gh-pages at 2026-10-10 23:47 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

Signed-off-by: riseproject-dev[bot] <330740410+riseproject-dev[bot]@users.noreply.github.com>
@riseproject-dev
riseproject-dev Bot force-pushed the github-actions/nightly-upgrade/wreq branch from 9ca3024 to 2ed9b6c Compare October 6, 2026 08:46
@riseproject-dev riseproject-dev Bot changed the title wreq: Add versions 0.12.2, 0.12.3 wreq: Add versions 0.12.2, 0.12.3, 0.13.0 Oct 6, 2026
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.
@luhenry
luhenry marked this pull request as ready for review October 11, 2026 03:27

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant