Release v6.0.0

[ixti]

No description provided.

[ixti]

@tarcieri if that looks good to you - I will cut the release

[tarcieri]

Are there actually any breaking changes?

[ixti]

I believe #776 and #783 are.

Also, I just noticed a PR that I wanted to merge 4 years ago and never get to it, that I believe we should add in the release. The change will be in how readpartial work to make it more IO-alike (raising EOFError when the end is reached instead of silent empty chunk). See: #618

[ixti]

Alternative - I can cherry pick retriable and headers caching and cut 5.3.0 release instead.

[tarcieri]

I’d definitely like to roll forward rather than backward, but v6.0.0 would be a great time to update the timeout subsystem: #773

[ixti]

Will merge #773

[tarcieri]

#773 is an issue, not a PR. Perhaps we should ping the people mentioned in that issue to see if they can open a PR, though

[ixti]

Oh, I have confused it with #754 indeed

[tarcieri]

I made a last call for breaking changes to the timeout subsystem in #773, though perhaps we should merge #754 first as well

[lineofflightagent]

Hey @ixti! 👋

I maintain the Peddler gem (Amazon SP-API client) and we'd love to use the :raise_error feature from #792 for our error handling. It's exactly what we need!

Since v6.0.0 seems blocked on breaking changes, would you consider that v5.3.0 release you mentioned in August? Cherry-picking the raise_error feature (plus retriable/headers caching) would help us and other downstream libraries adopt it immediately rather than waiting for v6.0.0.

Thanks for all the great work on HTTP! 🙏

[ixti]

After looking through the changes, I think it's fine to release 5.3.0 off the master by only excluding 1ba37c2, the rest looks fine for minor version bump. Doing that now

[ixti]

Released v5.3.0; Closing this ticket, as I agree we should add as many breaking changes as we can to avoid making major bumps a habbit ;D

[ixti]

Here's the list of backported commits: v5.2.0...v5.3.0