You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to install the latest version of AWS Encryption SDK for go fails
Command:
go version
go get github.com/aws/aws-encryption-sdk/releases/go/encryption-sdk@latest
Output:
go version go1.23.5 darwin/arm64
go: downloading github.com/aws/aws-encryption-sdk v4.1.0+incompatible
go: module github.com/aws/aws-encryption-sdk@latest found (v4.1.0+incompatible), but does not contain package github.com/aws/aws-encryption-sdk/releases/go/encryption-sdk
However, If try to download an earlier version of the SDK, I am able to do so
Command:
go get github.com/aws/aws-encryption-sdk/releases/go/encryption-sdk@v0.1.0
Output
go: downloading github.com/aws/aws-encryption-sdk/releases/go/encryption-sdk v0.1.0
go: warning: github.com/aws/aws-encryption-sdk/releases/go/encryption-sdk@v0.1.0: retracted by module author
go: to switch to the latest unretracted version, run:
go get github.com/aws/aws-encryption-sdk/releases/go/encryption-sdk@latest
go: added github.com/aws/aws-encryption-sdk/releases/go/encryption-sdk v0.1.0
You are right, we've retracted all the published versions of AWS Encryption SDK for Go due to an issue we identified recently. We are working on a fix for it but there's no date for it yet. As soon as the fix is published, you'll be able to pull in the new version. Thanks for reaching out to us!
Trying to install the latest version of AWS Encryption SDK for go fails
Command:
Output:
However, If try to download an earlier version of the SDK, I am able to do so
Command:
Output
I believe that the cause of this is #757
go.mod
file:retract [v0.0.0-0, v0.1.1]
v0.1.1
and would need to wait forv0.1.2
to be releasedWhat I am unclear on is whether or not this was intentional? According to this blog post https://aws.amazon.com/about-aws/whats-new/2025/01/aws-encryption-sdk-go-available/, this SDK is generally available.
The text was updated successfully, but these errors were encountered: