·
4 commits
to main
since this release
0.25.76
15th June, 2026.
I know that the automatic community review rates this repository badly. This repository contains a submodule, and the programme cannot parse that. However, I wrote a workaround and noticed, "What is a workaround for review...?". Placing a d.ts file would largely resolve the issue, but as this is never going to be a fundamental solution (or... ), I am reconsidering it. Or, shall we report?
Passing this test means the submodule will be a "verified" something, so I think it is better to have it fail, for now, at least.
Fixed
- Now the S3 connection with custom headers works properly (#875).
- Previously, custom headers injected for proxy authentication were incorrectly included in the AWS Signature v4 calculation. This led to a '400 Bad Request' error (such as 'signed header is not present') on strict S3 backends (for example, Garage), or when reverse proxies modified, renamed, or stripped these headers before they reached the storage service.
- No longer connection information of the P2P synchronisation is broken on the specific platform (#956).