Version 0.26.0

[karpetrosyan]

Chanelog

Added

• The proxy argument was added. You should use the proxy argument instead of the deprecated proxies, or use mounts= for more complex configurations. (Add the 'proxy' parameter and deprecate 'proxies'. #2879)

Deprecated

• The proxies argument is now deprecated. It will still continue to work, but it will be removed in the future. (Add the 'proxy' parameter and deprecate 'proxies'. #2879)

Fixed

• Fix cases of double escaping of URL path components. Allow / as a safe character in the query portion. Cleanup URL percent-encoding behavior. #2990.
• Handle NO_PROXY envvar cases when a fully qualified URL is supplied as the value. (Fix environment proxies #2741)
• Allow URLs where username or password contains unescaped '@'. (Allow URLs where username or password contains unescaped '@'. #2986)
• Ensure ASGI raw_path does not include URL query component. (Ensure that ASGI 'raw_path' does not include query component of URL. #2999)
• Ensure Response.iter_text() cannot yield empty strings. (Fixed iter_text adding an empty string #2998)

[karpetrosyan]

Here is the release draft: https://github.com/encode/httpx/releases/tag/untagged-0a9c39e62890eb69277d

[T-256]

Don't forget #2990

[tomchristie]

Thanks @T-256 - apologies for missing the CHANGELOG.md entry on that.

I'd suggest either this...

• Fix cases of double escaping of URL path components. Allow / as a safe character in the query portion. Cleanup URL percent-encoding behavior. #2990.

Or this...

• Ensure URL path components do not double escape when containing both unsafe chars and escape sequences. Allow / as a safe character in the query portion. Cleanup URL percent-encoding behavior. #2990.

[karpetrosyan]

Thanks @T-256

I think this one is better

Fix cases of double escaping of URL path components. Allow / as a safe character in the query portion. #2990.

[tomchristie]

I think this one is better

Ok. Let's go with that.

[karpetrosyan]

Should I schedule it for today?

[tomchristie]

That would be fine, yep.
Thanks so much, @karpetrosyan. 😄

[karpetrosyan]

Here is the new one: https://github.com/encode/httpx/releases/edit/untagged-893baae112e60ca1d83c

[tomchristie]

We might want to make it clear the proxies=... does still continue to work, but will raise a warning?

Looking great, thanks.

[karpetrosyan]

I'd recommend something like this.

0.26.0

Added

• The proxy argument was added. You should use the proxy argument instead of the deprecated proxies, or use mounts= for more complex configurations. (Add the 'proxy' parameter and deprecate 'proxies'. #2879)

Deprecated

• The proxies argument is now deprecated. It will still continue to work, but it will be removed in the future. (Add the 'proxy' parameter and deprecate 'proxies'. #2879)

[tomchristie]

Neat.

[karpetrosyan]

The final one: https://github.com/encode/httpx/releases/edit/untagged-8838a3cfc61a09bc35d6

[tomchristie]

Hrm... we don't seem to have triggered a publish event?

https://github.com/encode/httpx/actions/workflows/publish.yml

[tomchristie]

Ah okay, done.