Skip to content
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

fix(deploy): update dependency boto3 to v1.35.67 #20614

Merged
merged 1 commit into from
Nov 22, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 22, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
boto3 ==1.35.66 -> ==1.35.67 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

boto/boto3 (boto3)

v1.35.67

Compare Source

=======

  • api-change:apigateway: [botocore] Added support for custom domain names for private APIs.
  • api-change:application-autoscaling: [botocore] Application Auto Scaling now supports Predictive Scaling to proactively increase the desired capacity ahead of predicted demand, ensuring improved availability and responsiveness for customers' applications. This feature is currently only made available for Amazon ECS Service scalable targets.
  • api-change:appsync: [botocore] Add support for the Amazon Bedrock Runtime.
  • api-change:ce: [botocore] This release introduces three new APIs that enable you to estimate the cost, coverage, and utilization impact of Savings Plans you plan to purchase. The three APIs are StartCommitmentPurchaseAnalysis, GetCommitmentPurchaseAnalysis, and ListCommitmentPurchaseAnalyses.
  • api-change:cloudfront: [botocore] Adds support for Origin Selection between EMPv2 origins based on media quality score.
  • api-change:cloudtrail: [botocore] This release introduces new APIs for creating and managing CloudTrail Lake dashboards. It also adds support for resource-based policies on CloudTrail EventDataStore and Dashboard resource.
  • api-change:ec2: [botocore] Adds support for requesting future-dated Capacity Reservations with a minimum commitment duration, enabling IPAM for organizational units within AWS Organizations, reserving EC2 Capacity Blocks that start in 30 minutes, and extending the end date of existing Capacity Blocks.
  • api-change:elasticache: [botocore] Added support to modify the engine type for existing ElastiCache Users and User Groups. Customers can now modify the engine type from redis to valkey.
  • api-change:elbv2: [botocore] This feature adds support for enabling zonal shift on cross-zone enabled Application Load Balancer, as well as modifying HTTP request and response headers.
  • api-change:health: [botocore] Adds metadata property to an AffectedEntity.
  • api-change:iot: [botocore] General Availability (GA) release of AWS IoT Device Management - Commands, to trigger light-weight remote actions on targeted devices
  • api-change:iotfleetwise: [botocore] AWS IoT FleetWise now includes campaign parameters to store and forward data, configure MQTT topic as a data destination, and collect diagnostic trouble code data. It includes APIs for network agnostic data collection using custom decoding interfaces, and monitoring the last known state of vehicles.
  • api-change:iot-jobs-data: [botocore] General Availability (GA) release of AWS IoT Device Management - Commands, to trigger light-weight remote actions on targeted devices
  • api-change:lambda: [botocore] Adds support for metrics for event source mappings for AWS Lambda
  • api-change:logs: [botocore] Adds "Create field indexes to improve query performance and reduce scan volume" and "Transform logs during ingestion". Updates documentation for "PutLogEvents with Entity".
  • api-change:notifications: [botocore] This release adds support for AWS User Notifications. You can now configure and view notifications from AWS services in a central location using the AWS SDK.
  • api-change:notificationscontacts: [botocore] This release adds support for AWS User Notifications Contacts. You can now configure and view email contacts for AWS User Notifications using the AWS SDK.
  • api-change:resiliencehub: [botocore] AWS Resilience Hub's new summary view visually represents applications' resilience through charts, enabling efficient resilience management. It provides a consolidated view of the app portfolio's resilience state and allows data export for custom stakeholder reporting.
  • api-change:s3: [botocore] Add support for conditional deletes for the S3 DeleteObject and DeleteObjects APIs. Add support for write offset bytes option used to append to objects with the S3 PutObject API.
  • api-change:ssm: [botocore] Added support for providing high-level overviews of managed nodes and previewing the potential impact of a runbook execution.
  • api-change:ssm-quicksetup: [botocore] Add methods that retrieve details about deployed configurations: ListConfigurations, GetConfiguration
  • api-change:xray: [botocore] AWS X-Ray introduces Transaction Search APIs, enabling span ingestion into CloudWatch Logs for high-scale trace data indexing. These APIs support span-level queries, trace graph generation, and metric correlation for deeper application insights.

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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link

sonarcloud bot commented Nov 22, 2024

@mergify mergify bot merged commit a3a0d32 into main Nov 22, 2024
148 checks passed
@mergify mergify bot deleted the renovate/deploy-boto3-1.x branch November 22, 2024 03:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants