-
Notifications
You must be signed in to change notification settings - Fork 33
chore: update AWS SDK dependencies #999
New issue
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
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #999 +/- ##
===========================================
+ Coverage 77.86% 77.91% +0.05%
===========================================
Files 298 298
Lines 11643 11643
Branches 1393 1394 +1
===========================================
+ Hits 9066 9072 +6
+ Misses 2126 2121 -5
+ Partials 451 450 -1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…ert to version 2.9.3
end to end tests green https://github.com/aws-powertools/powertools-lambda-dotnet/actions/runs/17861831447 |
codecov safe to be ignored |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work on this one, I know it's been tedious to work with but I'm sure our customers will appreciate it.
Signed-off-by: Henrique Graca <999396+hjgraca@users.noreply.github.com>
|
Issue number: #900
Summary
Changes
This pull request primarily updates several AWS and related NuGet package dependencies to their latest versions across the codebase, and adjusts tests and code to accommodate these changes.
User experience
Checklist
Please leave checklist items unchecked if they do not apply to your change.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.