-
-
Notifications
You must be signed in to change notification settings - Fork 85
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
feat: Migrate S3 Client from AWS SDK v2 to v3 #231
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Thanks for opening this pull request! |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #231 +/- ##
==========================================
+ Coverage 95.60% 97.18% +1.57%
==========================================
Files 2 2
Lines 205 213 +8
Branches 44 0 -44
==========================================
+ Hits 196 207 +11
+ Misses 9 6 -3 ☔ View full report in Codecov by Sentry. |
mtrezza
changed the title
feat: Migrate S3 Client from AWS SDK v2 (deprecated) to v3
feat: Migrate S3 Client from AWS SDK v2 to v3
Jan 1, 2025
parseplatformorg
pushed a commit
that referenced
this pull request
Jan 1, 2025
# [4.0.0](3.0.0...4.0.0) (2025-01-01) ### Features * Migrate S3 Client from AWS SDK v2 to v3 ([#231](#231)) ([8ac6014](8ac6014)) ### BREAKING CHANGES * The AWS S3 credentials are now set under `s3overrides.credentials` instead of directly under the `s3overrides` key; see the [migration guide](https://github.com/parse-community/parse-server-s3-adapter?#migration-guide-from-3x-to-4x) for more details. ([8ac6014](8ac6014))
🎉 This change has been released in version 4.0.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Continuation of #221 as it has been merged without breaking change note.
Closes: #197