Update dependency boto3 to v1.36.2 #772
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
![red-hat-konflux[bot]](https://avatars.githubusercontent.com/in/296509?s=60&v=4){kind=small}
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
JAVGan
force-pushed
the
konflux/mintmaker/master/boto3-1.x
branch
from
744195d to
0442a77
Compare
JAVGan
approved these changes
Jan 20, 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.2Release Notes
boto/boto3 (boto3)
v1.36.2Compare Source
======
bedrock-runtime: [botocore] Allow hyphens in tool name for Converse and ConverseStream APIsdetective: [botocore] Doc only update for Detective documentation.ec2: [botocore] Release u7i-6tb.112xlarge, u7i-8tb.112xlarge, u7inh-32tb.480xlarge, p5e.48xlarge, p5en.48xlarge, f2.12xlarge, f2.48xlarge, trn2.48xlarge instance types.notifications: [botocore] Added support for Managed Notifications, integration with AWS Organization and added aggregation summaries for Aggregate Notificationssagemaker: [botocore] Correction of docs for "Added support for ml.trn1.32xlarge instance type in Reserved Capacity Offering"v1.36.1Compare Source
======
ecs: [botocore] The release addresses Amazon ECS documentation tickets.sagemaker: [botocore] Added support for ml.trn1.32xlarge instance type in Reserved Capacity Offeringv1.36.0Compare 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_supportedandwhen_requiredoptions - in code using theresponse_checksum_validationparameter 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_supportedandwhen_requiredoptions - in code using therequest_checksum_calculationparameter 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 - "after 5am on saturday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
To execute skipped test pipelines write comment
/ok-to-test.This PR has been generated by MintMaker (powered by Renovate Bot).