Closed renovate[bot] closed 3 weeks ago
This looks harmless enough, the DRF version bump corresponds to a newer version of Redoc.
However I did a double-take looking at the boto3 bump. This dependency is not referred to anywhere in the code. This seems to be the case also for Brotli, url_normalize ? I'll merge this and open a PR to check for unneeded dependencies.
This PR contains the following updates:
==1.35.51
->==1.35.54
==2024.7.1
->==2024.11.1
==0.7.1
->==0.7.2
Release Notes
boto/boto3 (boto3)
### [`v1.35.54`](https://redirect.github.com/boto/boto3/blob/HEAD/CHANGELOG.rst#13554) [Compare Source](https://redirect.github.com/boto/boto3/compare/1.35.53...1.35.54) \======= - api-change:`bedrock-agent`: \[`botocore`] Amazon Bedrock Knowledge Bases now supports using application inference profiles to increase throughput and improve resilience. - api-change:`docdb-elastic`: \[`botocore`] Amazon DocumentDB Elastic Clusters adds support for pending maintenance actions feature with APIs GetPendingMaintenanceAction, ListPendingMaintenanceActions and ApplyPendingMaintenanceAction - api-change:`logs`: \[`botocore`] This release introduces an improvement in PutLogEvents - api-change:`taxsettings`: \[`botocore`] Add support for supplemental tax registrations via these new APIs: PutSupplementalTaxRegistration, ListSupplementalTaxRegistrations, and DeleteSupplementalTaxRegistration. ### [`v1.35.53`](https://redirect.github.com/boto/boto3/blob/HEAD/CHANGELOG.rst#13553) [Compare Source](https://redirect.github.com/boto/boto3/compare/1.35.52...1.35.53) \======= - api-change:`amp`: \[`botocore`] Added support for UpdateScraper API, to enable updating collector configuration in-place - api-change:`autoscaling`: \[`botocore`] Adds bake time for Auto Scaling group Instance Refresh - api-change:`batch`: \[`botocore`] Add `podNamespace` to `EksAttemptDetail` and `containerID` to `EksAttemptContainerDetail`. - api-change:`elbv2`: \[`botocore`] Add UDP support for AWS PrivateLink and dual-stack Network Load Balancers - api-change:`glue`: \[`botocore`] Add schedule support for AWS Glue column statistics - api-change:`sagemaker`: \[`botocore`] SageMaker HyperPod adds scale-down at instance level via BatchDeleteClusterNodes API and group level via UpdateCluster API. SageMaker Training exposes secondary job status in TrainingJobSummary from ListTrainingJobs API. SageMaker now supports G6, G6e, P5e instances for HyperPod and Training. - api-change:`sesv2`: \[`botocore`] This release enables customers to provide the email template content in the SESv2 SendEmail and SendBulkEmail APIs instead of the name or the ARN of a stored email template. ### [`v1.35.52`](https://redirect.github.com/boto/boto3/blob/HEAD/CHANGELOG.rst#13552) [Compare Source](https://redirect.github.com/boto/boto3/compare/1.35.51...1.35.52) \======= - api-change:`appsync`: \[`botocore`] This release adds support for AppSync Event APIs. - api-change:`connect`: \[`botocore`] Updated the public documentation for the UserIdentityInfo object to accurately reflect the character limits for the FirstName and LastName fields, which were previously listed as 1-100 characters. - api-change:`datasync`: \[`botocore`] AWS DataSync now supports Enhanced mode tasks. This task mode supports transfer of virtually unlimited numbers of objects with enhanced metrics, more detailed logs, and higher performance than Basic mode. This mode currently supports transfers between Amazon S3 locations. - api-change:`ec2`: \[`botocore`] This release adds two new capabilities to VPC Security Groups: Security Group VPC Associations and Shared Security Groups. - api-change:`ecs`: \[`botocore`] This release supports service deployments and service revisions which provide a comprehensive view of your Amazon ECS service history. - api-change:`geo-maps`: \[`botocore`] Release of Amazon Location Maps API. Maps enables you to build digital maps that showcase your locations, visualize your data, and unlock insights to drive your business - api-change:`geo-places`: \[`botocore`] Release of Amazon Location Places API. Places enables you to quickly search, display, and filter places, businesses, and locations based on proximity, category, and name - api-change:`geo-routes`: \[`botocore`] Release of Amazon Location Routes API. Routes enables you to plan efficient routes and streamline deliveries by leveraging real-time traffic, vehicle restrictions, and turn-by-turn directions. - api-change:`keyspaces`: \[`botocore`] Adds support for interacting with user-defined types (UDTs) through the following new operations: Create-Type, Delete-Type, List-Types, Get-Type. - api-change:`network-firewall`: \[`botocore`] AWS Network Firewall now supports configuring TCP idle timeout - api-change:`opensearch`: \[`botocore`] This release introduces the new OpenSearch user interface (Dashboards), a new web-based application that can be associated with multiple data sources across OpenSearch managed clusters, serverless collections, and Amazon S3, so that users can gain a comprehensive insights in an unified interface. - api-change:`opensearchserverless`: \[`botocore`] Neo Integration via IAM Identity Center (IdC) - api-change:`redshift`: \[`botocore`] This release launches S3 event integrations to create and manage integrations from an Amazon S3 source into an Amazon Redshift database. - api-change:`redshift-serverless`: \[`botocore`] Adds and updates API members for the Redshift Serverless AI-driven scaling and optimization feature using the price-performance target setting. - api-change:`route53`: \[`botocore`] This release adds support for TLSA, SSHFP, SVCB, and HTTPS record types. - api-change:`sagemaker`: \[`botocore`] Added support for Model Registry Staging construct. Users can define series of stages that models can progress through for model workflows and lifecycle. This simplifies tracking and managing models as they transition through development, testing, and production stages. - api-change:`workmail`: \[`botocore`] This release adds support for Multi-Factor Authentication (MFA) and Personal Access Tokens through integration with AWS IAM Identity Center.tfranzel/drf-spectacular-sidecar (drf-spectacular-sidecar)
### [`v2024.11.1`](https://redirect.github.com/tfranzel/drf-spectacular-sidecar/compare/2024.7.1...2024.11.1) [Compare Source](https://redirect.github.com/tfranzel/drf-spectacular-sidecar/compare/2024.7.1...2024.11.1)astral-sh/ruff (ruff)
### [`v0.7.2`](https://redirect.github.com/astral-sh/ruff/blob/HEAD/CHANGELOG.md#072) [Compare Source](https://redirect.github.com/astral-sh/ruff/compare/0.7.1...0.7.2) ##### Preview features - Fix formatting of single with-item with trailing comment ([#14005](https://redirect.github.com/astral-sh/ruff/pull/14005)) - \[`pyupgrade`] Add PEP 646 `Unpack` conversion to `*` with fix (`UP044`) ([#13988](https://redirect.github.com/astral-sh/ruff/pull/13988)) ##### Rule changes - Regenerate `known_stdlibs.rs` with stdlibs 2024.10.25 ([#13963](https://redirect.github.com/astral-sh/ruff/pull/13963)) - \[`flake8-no-pep420`] Skip namespace package enforcement for PEP 723 scripts (`INP001`) ([#13974](https://redirect.github.com/astral-sh/ruff/pull/13974)) ##### Server - Fix server panic when undoing an edit ([#14010](https://redirect.github.com/astral-sh/ruff/pull/14010)) ##### Bug fixes - Fix issues in discovering ruff in pip build environments ([#13881](https://redirect.github.com/astral-sh/ruff/pull/13881)) - \[`flake8-type-checking`] Fix false positive for `singledispatchmethod` (`TCH003`) ([#13941](https://redirect.github.com/astral-sh/ruff/pull/13941)) - \[`flake8-type-checking`] Treat return type of `singledispatch` as runtime-required (`TCH003`) ([#13957](https://redirect.github.com/astral-sh/ruff/pull/13957)) ##### Documentation - \[`flake8-simplify`] Include caveats of enabling `if-else-block-instead-of-if-exp` (`SIM108`) ([#14019](https://redirect.github.com/astral-sh/ruff/pull/14019))Configuration
📅 Schedule: Branch creation - "before 7am on monday" (UTC), 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.