Update dependency niquests to v3.21.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
niquests (changelog)	==3.20.1 → ==3.21.0

---

Release Notes

jawah/niquests (niquests)

v3.21.0

Compare Source

Added

• First-class support for the WebAssembly System Interface (WASI) Component Model. (#​364)

  Niquests can now run inside sandboxed WebAssembly components using the same
  Requests-compatible API available on native Python. This enables HTTP clients for
  edge functions, plug-ins, agent runtimes, and other capability-constrained
  applications without requiring application-specific adapters.

  Niquests automatically discovers the interfaces imported by the component and
  selects the most capable available transport. Synchronous applications can use
  native WASI Preview 2 sockets, while asynchronous applications can use Preview 3
  sockets. The socket transports retain urllib3.future's native behavior, including
  connection pooling, HTTP/2 multiplexing, streaming, trailers, WebSocket, SSE,
  redirects, retries, cookies, and timeout handling.

  Components that intentionally omit raw socket authority can instead use the
  host-managed wasi:http interfaces: HTTP 0.2 for synchronous applications and
  HTTP 0.3 for asynchronous applications. This provides a narrower capability surface
  in which the host controls DNS, TCP, TLS, certificate trust, protocol negotiation,
  and connection reuse. Niquests also supports hybrid worlds, using sockets where
  possible and WIT HTTP where host-managed TLS is required.

  No network or filesystem authority is ambient under WASI. A component's WIT world
  declares which interfaces it can access, while the runtime independently decides
  which capabilities to grant. Native hostname resolution therefore requires an
  explicit DNS grant, and host filesystem access remains unavailable unless a
  directory is deliberately preopened.

  HTTPS over native WASI sockets requires the rtls extra and urllib3.future
  2.24.900 or newer. When using WIT HTTP, TLS is provided according to the host's
  security policy instead.

  With this release, Niquests supports native Python, browser-side WebAssembly through
  Pyodide, and server-side WebAssembly through WASI while preserving the same familiar
  request API. See the WASI quickstart and advanced capability guide for deployment
  examples and transport-specific constraints.

• Explicit support for Python 3.15

• Custom json_encoder in Session and AsyncSession for request bodies. (#​437)

• Top-level request APIs accept custom JSON encoders and TLS configuration.

Fixed

• CRL or OCSP unparsable/corrupted may raise CryptoError. (#​430)
• A demoted (i.e. failed) HTTP/3 upgrade attempt could be retried when it should be permanently disabled. (#​431)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.