use `fetch.h1KeepAlive()` to avoid weird `Protocol Errors`

[tripodsan]

word2md often shows:

message:/drives/b!SRYzYQL770qsQPbhXU8sWMnBDDbKRg1Npp5iKHaWz7cyd_ev_i2JTI5LB0GcN0hc/items/01HFRI53KHKB4BUN6ENJG242X5SRIA4AXV/content: 
500 - Protocol error - FetchError: Protocol error

assuming something goes wrong with the h2 connection. maybe it's better to be on the safe side and use h1.

[stefan-guggisberg]

Background:

Azure endpoints/gateways may occasionally downgrade the protocol from h2 to h1, i.e. an azure endpoint which accepted h2 connections so far may suddenly only accept h1 connections. Sending an h2 request then results in a ERR_HTTP2_ERROR Protocol error.

[github-actions]

🎉 This issue has been resolved in version 6.2.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀