CodeSampleX

Recordsgolanggithub.com/aws/aws-sdk-go-v2failure issue

Failure signature

PROJECT_RESOLVE exit 1 ×2

<path>:<n>:<n>: missing go.sum entry for module providing package github.com/aws/smithy-go/auth/bearer (imported by github.com/aws/aws-sdk-go-v2/aws); to add: …

Evidence quality: complete · go/module · resolve-diagnostic · outer go run · First recorded: 2026-10-09 · Last seen: 2026-10-12

sha256:85e62dabaeaa…

github.com/aws/aws-sdk-go-v2/aws.AnonymousCredentials github.com/aws/aws-sdk-go-v2/aws.ClientLogMode github.com/aws/aws-sdk-go-v2/aws.Config github.com/aws/aws-sdk-go-v2/aws.CredentialsProvider github.com/aws/aws-sdk-go-v2/aws.LogRequest github.com/aws/aws-sdk-go-v2/aws.LogRetries github.com/aws/aws-sdk-go-v2/aws.LogSigning

Where it was measured

PASS means the release recorded a passing observation at PROJECT_RESOLVE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

Where it reproduced

Nearest known PASS/FAIL boundaries

No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Libraryv1.47.3v1.47.0v1.41.7
github.com/aws/smithy-go v1.28.5 v1.28.5 v1.25.1

Moved: 1 · unchanged at every release: 0

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.

Evidence gaps

Published answers for the affected releases

Back to the package