-
Notifications
You must be signed in to change notification settings - Fork 469
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
Update dependency boto3 to v1.36.0 #1551
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
7804b4e
to
c01ad52
Compare
07646c9
to
a57dc9e
Compare
652f542
to
2de9396
Compare
2de9396
to
50f889b
Compare
50f889b
to
1a06706
Compare
1a06706
to
292c200
Compare
7b4bff3
to
7af8d7d
Compare
7af8d7d
to
93a7240
Compare
93a7240
to
69fb610
Compare
69fb610
to
d6832a8
Compare
3c4fe3e
to
1e73a34
Compare
1e73a34
to
606cd56
Compare
606cd56
to
89174af
Compare
89174af
to
74e3ed9
Compare
74e3ed9
to
0b7b7d8
Compare
0b7b7d8
to
cd4897c
Compare
cd4897c
to
fdb8ee4
Compare
fdb8ee4
to
e1cf447
Compare
56638b4
to
e9d2553
Compare
e9d2553
to
1fb8983
Compare
1fb8983
to
6cccc66
Compare
ometelytsia
approved these changes
Jan 16, 2025
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.
This PR contains the following updates:
==1.35.99
->==1.36.0
Release Notes
boto/boto3 (boto3)
v1.36.0
Compare Source
======
apigateway
: [botocore
] Documentation updates for Amazon API Gatewaybedrock-agent-runtime
: [botocore
] Now supports streaming for inline agents.cognito-identity
: [botocore
] corrects the dual-stack endpoint configurationpartnercentral-selling
: [botocore
] Add Tagging support for ResourceSnapshotJob resourcess3
: [botocore
] This change enhances integrity protections for new SDK requests to S3. S3 SDKs now support the CRC64NVME checksum algorithm, full object checksums for multipart S3 objects, and new default integrity protections for S3 requests.security-ir
: [botocore
] Increase minimum length of Threat Actor IP 'userAgent' to 1.sesv2
: [botocore
] This release introduces a new recommendation in Virtual Deliverability Manager Advisor, which detects elevated complaint rates for customer sending identities.workspaces
: [botocore
] Added GeneralPurpose.4xlarge & GeneralPurpose.8xlarge ComputeTypes.workspaces-thin-client
: [botocore
] Mark type in MaintenanceWindow as required.botocore
] Update awscrt version to 0.23.4s3
: [botocore
] The S3 client attempts to validate response checksums for all S3 API operations that support checksums. However, if the SDK has not implemented the specified checksum algorithm then this validation is skipped. Checksum validation behavior can be configured using thewhen_supported
andwhen_required
options - in code using theresponse_checksum_validation
parameter forbotocore.config.Config
, in the shared AWS config file usingresponse_checksum_validation
, or as an env variable usingAWS_RESPONSE_CHECKSUM_VALIDATION
.s3
: [botocore
] Added support for the CRC64NVME checksum algorithm in the S3 client through the optional AWS CRT (awscrt
) dependency.s3
: [botocore
] S3 client behavior is updated to always calculate a CRC32 checksum by default for operations that support it (such as PutObject or UploadPart), or require it (such as DeleteObjects). Checksum behavior can be configured usingwhen_supported
andwhen_required
options - in code using therequest_checksum_calculation
parameter forbotocore.config.Config
, in the shared AWS config file usingrequest_checksum_calculation
, or as an env variable usingAWS_REQUEST_CHECKSUM_CALCULATION
. Note: Botocore will no longer automatically compute and populate the Content-MD5 header.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.