CLDSRV-932: validate x-amz-content-sha256#6208
Conversation
Hello leif-scality,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the |
| "@opentelemetry/instrumentation-mongodb": "~0.69.0", | ||
| "@smithy/node-http-handler": "^3.0.0", | ||
| "arsenal": "git+https://github.com/scality/arsenal#8.5.0", | ||
| "arsenal": "git+https://github.com/scality/arsenal#improvement/ARSN-602-add-XAmzContentSHA256Mismatch-error", |
There was a problem hiding this comment.
Arsenal is pinned to a branch (improvement/ARSN-602-add-XAmzContentSHA256Mismatch-error), not a tag. Git-based deps must pin to a release tag before merging.
Codecov Report❌ Patch coverage is
Additional details and impacted files
... and 1 file with indirect coverage changes @@ Coverage Diff @@
## development/9.4 #6208 +/- ##
===================================================
+ Coverage 85.51% 85.52% +0.01%
===================================================
Files 210 211 +1
Lines 14239 14312 +73
===================================================
+ Hits 12177 12241 +64
- Misses 2062 2071 +9
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
969e37f to
ffbc547
Compare
ffbc547 to
e9c49e2
Compare
…ject, UploadPart)
e9c49e2 to
28a36c3
Compare
Reject a
SigV4request if thesha256of the body does not match thex-amz-content-sha256header