The HTTP client major is the break your AE never sees

So Got shipped v16.0.0 last night. We flagged it Important as a breaking change. To the best of my understanding that's the right call, even though nobody on a sales team is watching a Node HTTP client.

They rewrote HTTP/2 and dropped the http2-wrapper dependency. Built-in client now, with ALPN and a pooled session cache. HTTP/2 proxy support is gone. It came from that wrapper. They said it was very buggy anyway. If you still need a proxy, you keep using http2-wrapper through the request option. Returning a request from there bypasses Got's own HTTP/2 client.

Kind of easy to file this under library bump. I keep doing that. Then a customer who talks HTTP/2 through a corporate proxy files a ticket and the account team has no idea a major landed.

Same release, agent.http2 is no longer an agent slot. Pass false to skip pooling. Pass an agent instance and it throws. Response headers no longer carry :status. You use response.statusCode. Let's say you had a beforeRequest hook, an afterResponse retry, or a pagination step that moved the request to a different origin. authorization, cookie, cookie2, host, and proxy-authorization get stripped, URL credentials drop, and an unchanged body is cleared unless you set them again inside the hook. copyPipedHeaders stopped forwarding credentials too. The old searchParameters, followRedirects, and auth stubs now throw Unexpected option.

That's the partner-break, just one layer down from the vendor changelog your AE already watches. That feed never mentions Got. The product still embeds it.

We pull it into a uniform entry shape at /sources/got-releases. Same JSON as everything else. The talking point is proxy support is gone, and passing an http2 agent throws. The new QUERY method and dropping cacheable-lookup are decoration.