fix(deps): update all dependencies
This MR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| boto3 | dependencies | minor |
1.35.97 -> 1.36.2
|
| moto (changelog) | dev | patch |
5.0.26 -> 5.0.27
|
| responses (changelog) | dev | patch |
0.25.5 -> 0.25.6
|
| uis/devops/continuous-delivery/ci-templates | repository | minor |
v6.4.4 -> v6.5.0
|
Release Notes
boto/boto3 (boto3)
v1.36.2
======
- api-change:
bedrock-runtime: [botocore] Allow hyphens in tool name for Converse and ConverseStream APIs - api-change:
detective: [botocore] Doc only update for Detective documentation. - api-change:
ec2: [botocore] Release u7i-6tb.112xlarge, u7i-8tb.112xlarge, u7inh-32tb.480xlarge, p5e.48xlarge, p5en.48xlarge, f2.12xlarge, f2.48xlarge, trn2.48xlarge instance types. - api-change:
notifications: [botocore] Added support for Managed Notifications, integration with AWS Organization and added aggregation summaries for Aggregate Notifications - api-change:
sagemaker: [botocore] Correction of docs for "Added support for ml.trn1.32xlarge instance type in Reserved Capacity Offering"
v1.36.1
======
- api-change:
ecs: [botocore] The release addresses Amazon ECS documentation tickets. - api-change:
sagemaker: [botocore] Added support for ml.trn1.32xlarge instance type in Reserved Capacity Offering
v1.36.0
======
- api-change:
apigateway: [botocore] Documentation updates for Amazon API Gateway - api-change:
bedrock-agent-runtime: [botocore] Now supports streaming for inline agents. - api-change:
cognito-identity: [botocore] corrects the dual-stack endpoint configuration - api-change:
partnercentral-selling: [botocore] Add Tagging support for ResourceSnapshotJob resources - api-change:
s3: [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. - api-change:
security-ir: [botocore] Increase minimum length of Threat Actor IP 'userAgent' to 1. - api-change:
sesv2: [botocore] This release introduces a new recommendation in Virtual Deliverability Manager Advisor, which detects elevated complaint rates for customer sending identities. - api-change:
workspaces: [botocore] Added GeneralPurpose.4xlarge & GeneralPurpose.8xlarge ComputeTypes. - api-change:
workspaces-thin-client: [botocore] Mark type in MaintenanceWindow as required. - enhancement:AWSCRT: [
botocore] Update awscrt version to 0.23.4 - feature:
s3: [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. - feature:
s3: [botocore] Added support for the CRC64NVME checksum algorithm in the S3 client through the optional AWS CRT (awscrt) dependency. - feature:
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.
v1.35.99
=======
- api-change:
gamelift: [botocore] Amazon GameLift releases a new game session placement feature: PriorityConfigurationOverride. You can now override how a game session queue prioritizes placement locations for a single StartGameSessionPlacement request. - api-change:
route53: [botocore] Amazon Route 53 now supports the Mexico (Central) Region (mx-central-1) for latency records, geoproximity records, and private DNS for Amazon VPCs in that region
v1.35.98
=======
- api-change:
artifact: [botocore] Support resolving regional API calls to partition's leader region endpoint. - api-change:
bedrock: [botocore] With this release, Bedrock Evaluation will now support latency-optimized inference for foundation models. - api-change:
ec2: [botocore] Add support for DisconnectOnSessionTimeout flag in CreateClientVpnEndpoint and ModifyClientVpnEndpoint requests and DescribeClientVpnEndpoints responses - api-change:
kafkaconnect: [botocore] Support updating connector configuration via UpdateConnector API. Release Operations API to monitor the status of the connector operation. - api-change:
transcribe: [botocore] This update provides tagging support for Transcribe's Call Analytics Jobs and Call Analytics Categories.
getmoto/moto (moto)
v5.0.27
Docker Digest for 5.0.27: sha256:ac5312f68c6b748b667526025f9e7a8c2e4112837c258eee68f96fa36d9dbbef
New Methods:
* Glue:
* create_dev_endpoint()
* get_dev_endpoint()
* get_dev_endpoints()
* KMS:
* generate_mac()
* list_key_rotations()
* rotate_key_on_demand()
* verify_mac()
* SES:
* delete_configuration_set()
* list_configuration_sets()
* SESv2:
* create_configuration_set()
* create_dedicated_ip_pool()
* delete_configuration_set()
* delete_dedicated_ip_pool()
* get_configuration_set()
* get_dedicated_ip_pool()
* list_configuration_sets()
* list_dedicated_ip_pools()
Miscellaneous:
* Introduced a new setting for ServerMode, `MOTO_DISABLE_GLOBAL_CORS`. Disabling the global CORS setting makes it possible to test the CORS-policies on S3 buckets
* ElastiCache: create_user() now supports the AuthenticationMode-parameter
* ElasticSearch/OpenSearch: list_domain_names() now returns domains from both services
* Kafka: list_clusters_v2() now returns all parameters
* Scheduler: The `schedule_expression_timezone` now defaults to UTC
* RDS: create_db_instance() now throws an exception if an instance with that ID already exists
* RDS: restore_db_instance_from_db_snapshot() now throws an exception if an instance with that ID already exists
uis/devops/continuous-delivery/ci-templates (uis/devops/continuous-delivery/ci-templates)
v6.5.0
Configuration
-
If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.
Edited by uis-devops-renovatebot