github.com/aws/aws-sdk-go-v2/service/s3
- 1.88.4 changes default checksum behaviour for presigned uploads; TestPresignedUpload fails reproducibly with it.
Evidence trail
Every step Darwin took, from the records it keeps
Found behind latest
github.com/aws/aws-sdk-go-v2/service/s3 1.84.1 is declared in go.mod; the registry's latest is 1.88.4.
Compared the release's API
CI on PR #90 failed reproducibly with 1.88.4: TestPresignedUpload expects the old checksum header. The CI repair round re-ran the job with act on base and head, then proposed the newest older release that passes.
Candidate Result Reason 1.88.4 Nothing found no API difference the reviewer could confirm Validated with 389 tests
Each check ran on the unmodified repository first; only checks that pass there judge the change. One repair attempt ran after the first failure.
Check From Unmodified With change Tests go build ./... go.yml · test Passed Passed — go test -race ./... go.yml · test Passed Passed 389 Review gate approved the patch
Fallback moves only the s3 module and its own indirect requirements.
DeepSeek V4.1 Flash
Opened #90 as a draft
Update github.com/aws/aws-sdk-go-v2/service/s3 to 1.87.3. Your repository's own CI judged it: CI passed
Check Workflow Verdict Note test go.yml Passed 5 min CI repair round. Reproduced TestPresignedUpload failing on head and passing on base; pushed a commit moving s3 to 1.87.3. Comment-only gate: a human marks it ready.Waiting for a person to merge
CI repair moved the PR to 1.87.3; 1.88.4 is held with its evidence.
Summary
- Repository
- acme/billing-service
- Present
- 1.84.1
- Latest
- 1.88.4
- Proposed
- 1.87.3
- Kind
- Version update
- Checked
- Oct 24, 02:21 UTC
- Pull request
- Ready for review#90
- Reviewers
- jordan
1.88.4 held
Proposed 1.87.3 instead
Held because a check that passes on the unmodified repository fails reproducibly with this release, and the application-code migration did not fix it.
For agents
The same record, over MCP
dovel_get_update({
id: "billing-service--s3"
})