We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
According to this https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-go-v1-on-july-31-2025/, there will be no more releases for AWS SDK for Go v1 after July 2025. AWS as maintainer of this AWS SDK for Go package announced the EOL of the version 1 for July 31, 2025. After this date, there are no critical bug fixes and no security issues provided.
alertmanager/go.mod
Line 9 in b5d1a64
Prometheus Alertmanager should consider migrating to AWS SDK for Go v2 - https://github.com/aws/aws-sdk-go-v2/ so that we reduce the technical dept and prometheus converges to use a single version of this SDK.
I'm going to link the same topic in other components in the Prometheus ecosystem: prometheus/prometheus#15572 prometheus/sigv4#14
The text was updated successfully, but these errors were encountered:
No branches or pull requests
According to this https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-go-v1-on-july-31-2025/,
there will be no more releases for AWS SDK for Go v1 after July 2025. AWS as maintainer of this AWS SDK for Go package announced the EOL of the version 1 for July 31, 2025. After this date, there are no critical bug fixes and no security issues provided.
alertmanager/go.mod
Line 9 in b5d1a64
Prometheus Alertmanager should consider migrating to AWS SDK for Go v2 - https://github.com/aws/aws-sdk-go-v2/ so that we reduce the technical dept and prometheus converges to use a single version of this SDK.
I'm going to link the same topic in other components in the Prometheus ecosystem:
prometheus/prometheus#15572
prometheus/sigv4#14
The text was updated successfully, but these errors were encountered: