v1.0.1

• A lowercase method (get) is signed as upper case (GET), as botocore does. fetch sends get, put, post, delete, head and options in upper case, so before this the signature did not match and the service answered SignatureDoesNotMatch. Node's fetch sends patch as written, so pass PATCH in upper case to both sigflint and fetch.
• end(trailers) on a chunk signer throws a TypeError when a trailer name or value holds a line break. Before, the break was signed as another trailer line.
• Correction to the 1.0.0 entry: a raw + in an S3 path is signed as a space, but "as S3 reads it" was not verified. Nothing has been tried against AWS S3, and a local s3s-fs 0.17.0 server reads a raw + as a plus sign and rejected the signature. Write %2B in the URL to mean a plus: that server accepted it from sigflint and from botocore. The signing is unchanged (docs/guide.md).
• Correction to the 1.0.0 entry: a bundler that picks the node or bun condition gets the built file (dist/) and drops unused signers just as well; the per-signer modules (src/) go to the workerd, worker and browser conditions and to bundlers that match none of them.