Skip to content

Update dependency boto3 to ~=1.43.13#2199

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/boto3-1.x
Open

Update dependency boto3 to ~=1.43.13#2199
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/boto3-1.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 2, 2026

This PR contains the following updates:

Package Change Age Confidence
boto3 ~=1.42.0~=1.43.13 age confidence

Release Notes

boto/boto3 (boto3)

v1.43.13

Compare Source

=======

  • api-change:batch: [botocore] Clarified CreateComputeEnvironment parameter requirements - serviceRole is required for UNMANAGED compute environments, allocationStrategy is required for EKS compute environments, and compute environments must be created in the ENABLED state.
  • api-change:bedrock-agentcore-control: [botocore] Adds dataset management APIs for creating, versioning, and managing evaluation datasets.
  • api-change:cleanrooms: [botocore] Collaboration creators can update payment configurations without recreating the collaboration. When multiple payer candidates are configured for a cost type, analysis runners can specify the actual payer at submission time, providing granular control over billing.
  • api-change:cleanroomsml: [botocore] Collaboration creators can update payment configurations without recreating the collaboration. When multiple payer candidates are configured for a cost type, analysis runners can specify the actual payer at submission time, providing granular control over billing.
  • api-change:evs: [botocore] A new GetDepotUrl API has been added to retrieve a URL for accessing Amazon EVS custom addon packages. Customers can use this URL to configure vSphere Lifecycle Manager (vLCM) as an online depot source, enabling upgrades of addon components across ESXi hosts.
  • api-change:mediaconnect: [botocore] Adds support for controlling the timecode source of NDI flow outputs.
  • api-change:sagemaker: [botocore] Add support for disabling home EFS file system creation on SageMaker domains.
  • api-change:verifiedpermissions: [botocore] Support hard deleting policy store aliases. Users can now delete an alias and immediately reassign it to a different policy store without waiting for the soft-delete retention period.

v1.43.12

Compare Source

=======

  • api-change:bedrock-runtime: [botocore] Supporting Request Metadata for Invoke Model and Invoke Model with Response Stream
  • api-change:customer-profiles: [botocore] Amazon Connect Customer Profiles adds support for item catalog columns in RecommenderSchema, ExcludedColumns in Create and Update Recommender to specify columns to exclude from training, and the ability to disable automatic retraining by setting TrainingFrequency to 0.
  • api-change:kms: [botocore] AWS KMS now supports creating grants for AWS service principals using new GranteeServicePrincipal and RetiringServicePrincipal parameters. This release adds SourceArn grant constraint and three condition keys for controlling CreateGrant access. For more information, see Grants in AWS KMS.
  • api-change:mwaa: [botocore] Updated API documentation to describe the PublicAndPrivate webserver access mode.
  • api-change:payment-cryptography-data: [botocore] GenerateAuthRequestCryptogram API launch.

v1.43.11

Compare Source

=======

  • api-change:bedrock-agentcore: [botocore] Add RetryableConflictException (HTTP 409) to InvokeAgentRuntime and StopRuntimeSession to prevent orphaned VMs during concurrent session access. The SDK automatically retries this exception with backoff. Enforcement is not yet active and will be enabled in a future service update.
  • api-change:devops-agent: [botocore] Added a new serviceType mcpserversigv4 service and association. This provides feature to register MCP sigv4 authorization based MCPs
  • api-change:grafana: [botocore] Introduce degraded workspace status as a possible Amazon Managed Grafana workspace status, and a new field named degraded workspace reason which informs customers why the workspace is degraded in the DescribeWorkspace API response.
  • api-change:guardduty: [botocore] Adding support for exposure and vulnerability context from AWS Security Hub in GuardDuty Extended Threat Detection attack sequence findings.
  • api-change:rtbfabric: [botocore] This release is to deprecate 'inboundLinksCount' field in GetResponderGateway response and introduce the new field 'linksRequestedCount' to replace it.
  • api-change:sagemaker: [botocore] Add support for ml.p5.4xlarge and ml.p5en.48xlarge instances on SageMaker Notebook Instances Platform.

v1.43.10

Compare Source

=======

  • api-change:accessanalyzer: [botocore] Services manage service-linked analyzers through dedicated APIs - CreateServiceLinkedAnalyzer and DeleteServiceLinkedAnalyzer that separate service-linked specific operations from customer-managed operations. It also shows up in ListAnalyzers and GetAnalyzer responses.
  • api-change:connect: [botocore] Amazon Connect Cases now supports SLA durations of up to 2 years (1,051,200 minutes), increased from the previous maximum of 90 days (129,600 minutes). This enables you to track long-running service level agreements for cases that require extended resolution timelines.
  • api-change:ec2: [botocore] Amazon VPC IP Address Manager (IPAM) now supports tags on IPAM pool allocations, enabling all standard tagging features for allocations including tag-on-create.
  • api-change:ecs: [botocore] Amazon ECS now supports Pause lifecycle hooks for service deployments, allowing customers to automatically pause deployments at specified stages and use the new ContinueServiceDeployment API to continue or roll back with confidence.
  • api-change:evs: [botocore] Amazon EVS now supports up to 32 hosts per EVS environment, increasing the previous host limit to allow a larger scale of VMware workload deployments and reduce operational overhead.
  • api-change:ivs: [botocore] Adds support for up to 3 mediaTailorPlaybackConfiguration objects in an ad configuration resource
  • api-change:quicksight: [botocore] Support for dataset enrichment and geo spatial in new data preparation experience

v1.43.9

Compare Source

======

  • api-change:logs: [botocore] Updating the max limit for start query api parameter.
  • api-change:mediapackagev2: [botocore] This release adds support for AvailabilityStartTimeConfiguration in MediaPackageV2 DASH manifests
  • api-change:partnercentral-selling: [botocore] Enable TCV intake on Opportunity to improve Opportunities Hygiene and downstream revenue attribution.

v1.43.8

Compare Source

======

  • api-change:bedrock: [botocore] Advanced Prompt Optimization (AdvPO) allows you to optimize and migrate your prompts for any model on Bedrock by automatically evaluating responses and rewriting prompts to improve performance. This release provides a programmatic way to create, get, list, stop, and delete AdvPO jobs.
  • api-change:cloudfront: [botocore] Adding a new boolean for OCSP Revocations in Viewer mTLS Create and Update APIs, and adding a new 'Passthrough' option for TrustStore modes
  • api-change:datazone: [botocore] Adds support for SageMaker Unified Studio notebook operations, including notebook import and export
  • api-change:dms: [botocore] Add 9 SDK waiters for DMS Schema Conversion async operations. Eliminates manual polling for import, assessment, conversion, export, and creation jobs.
  • api-change:glue: [botocore] Release --has-databases parameter for AWS Glue get-catalogs API, which filters catalog responses to include only those capable of containing databases, excluding parent catalogs that hold only other catalogs. Remove model-level validation on partition index list size for AWS Glue tables.
  • api-change:grafana: [botocore] Adds support for dual-stack (IPv4 and IPv6) connectivity to Amazon Managed Grafana workspaces. Customers can configure the ipAddressType parameter when creating or updating a workspace to choose between IPv4-only or dual-stack (IPv4 and IPv6) access.
  • api-change:mgn: [botocore] Introducing new option for security groups mapping - with MAP-DHCP the service translates security rules from your source environment with DHCP compatibility.
  • api-change:qconnect: [botocore] ListModels is an API that returns the available AI models for a Connect Assistant based on its region and AI prompt type.

v1.43.7

Compare Source

======

  • api-change:arc-region-switch: [botocore] Adds support for enabling and disabling Lambda event source mappings in Region switch plans.
  • api-change:batch: [botocore] Adds a billing callout to docs regarding using the CE Scale Down Delay feature
  • api-change:bedrock-agentcore-control: [botocore] Adds support for read-only summary APIs for Policy Engine, Policy, and Policy Generation resources, enabling metadata retrieval without KMS decryption for AWS Config integration.
  • api-change:billingconductor: [botocore] Add ConflictException to UpdateCustomLineItem operation.
  • api-change:connect: [botocore] This change added three new EventSourceName for schedule notification feature
  • api-change:connectcampaignsv2: [botocore] This release added support for Outbound Campaign timezone detection using all available contact methods
  • api-change:connectcases: [botocore] Amazon Connect Cases now supports SLA durations of up to 2 years (1,051,200 minutes), increased from the previous maximum of 90 days (129,600 minutes). This enables you to track long-running service level agreements for cases that require extended resolution timelines.
  • api-change:dsql: [botocore] Added support for Amazon Aurora DSQL change data capture (CDC) streams that deliver row-level database changes to Amazon Kinesis in JSON format. Includes CreateStream, GetStream, ListStreams, and DeleteStream operations.
  • api-change:ec2: [botocore] Include length limits in the SDK and documentation for text fields in Image (AMI) APIs such as the image name and description
  • api-change:endpoint-rules: [botocore] Update endpoint-rules client to latest version
  • api-change:es: [botocore] Adds support for AutomatedSnapshotPauseOptions.
  • api-change:glue: [botocore] AWS Glue now defaults the job timeout to 480 minutes for Glue version 5.0 and later when no timeout value is specified. The default remains 2,880 minutes for Glue version 4.0 and earlier.
  • api-change:lightsail: [botocore] Added OriginIpAddressTypeEnum (ipv4, ipv6, dualstack) and ipAddressType field to Origin and InputOrigin structures for Lightsail CDN distributions. Allows customers to specify how the distribution connects to origins, using IPv4, IPv6, or dualstack networking
  • api-change:opensearch: [botocore] Adds support for AutomatedSnapshotPauseOptions.
  • api-change:partnercentral-account: [botocore] Added ServiceQuotaExceededExceptions for Profile operations
  • api-change:pcs: [botocore] Add support for Amazon EC2 Interruptible-ODCR
  • api-change:quicksight: [botocore] Adds five new custom permission option for Quick Apps so that these capabilities can be controlled by public SDK and CLI.
  • api-change:redshift: [botocore] Added rg.xlarge and rg.4xlarge to valid NodeType values and updated documentation for CreateCluster, ModifyCluster, ResizeCluster, and RestoreFromClusterSnapshot APIs to reflect RG node type support.
  • api-change:rtbfabric: [botocore] Customers can now configure custom domain names for their RTB Fabric gateways. This enables partners to use their own branded domain for RTB traffic instead of the default rtbfabric endpoint
  • api-change:sagemaker: [botocore] Adds execution role session name mode to reflect user identity in Studio. Adds Flexible Training Plans on Studio apps. Adds restricted model packages to control access to proprietary model artifacts via IAM. Fixed instance type parity between inference endpoints and managed shadow tests.
  • api-change:securityagent: [botocore] Add support for code reviews, a new resource type that enables automated security-focused static analysis of source code repositories.
  • api-change:socialmessaging: [botocore] Adds parameters to call the GetWhatsAppMessageTemplate and UpdateWhatsAppMessageTemplate APIs with a template name and language code in place of the template ID. Linked WhatsApp accounts also describe whether the WABA is onboarded to Meta's Marketing Messages API.
  • api-change:stepfunctions: [botocore] Updated default SDK endpoints for AWS Step Functions in AWS GovCloud (US) regions. The default Dual-Stack endpoints now resolve to "states-fips" prefixed hostnames. There are no changes to service behavior. No customer action is required.

v1.43.6

Compare Source

======

  • api-change:bcm-data-exports: [botocore] With this release, customers can configure their data exports to generate additional integration artifacts for Athena and Redshift.
  • api-change:bedrock-agentcore: [botocore] Launching AgentCore payments - a capability that provides secure, instant microtransaction payments for AI agents to access paid APIs, MCP servers, and content. It handles payment processing for x402 protocol, payment limits, and 3P wallet integrations with Coinbase CDP and Stripe (Privy).
  • api-change:bedrock-agentcore-control: [botocore] Launching AgentCore payments - a capability that provides secure, instant microtransaction payments for AI agents to access paid APIs, MCP servers, and content. It handles payment processing for x402 protocol, payment limits, and 3P wallet integrations with Coinbase CDP and Stripe (Privy).
  • api-change:ec2: [botocore] DescribeInstanceTypes now accepts an IncludeUnsupportedInRegion parameter. When set, the response also lists instance types that are not available in the current Region. Each instance type includes a SupportedInRegion field indicating its regional availability.
  • api-change:guardduty: [botocore] This is a documentation update
  • api-change:invoicing: [botocore] Updated ListInvoiceSummaries API to add new ReceiverRole filter in Request and Response
  • api-change:route53resolver: [botocore] Adds supports for DNS64 on inbound endpoints and IPv6 forwarding through the internet gateway (IGW) on outbound endpoints, making it easier to manage hybrid DNS across IPv4 and IPv6 networks.

v1.43.5

Compare Source

======

  • api-change:bedrock-agentcore-control: [botocore] Adds support for bring-your-own file system in AgentCore Runtime. Developers can mount Amazon S3 Files and Amazon EFS access points directly into agent sessions using filesystemConfigurations.
  • api-change:endpoint-rules: [botocore] Update endpoint-rules client to latest version
  • api-change:glue: [botocore] Adds support for a CustomLogGroupPrefix parameter in StartDataQualityRulesetEvaluationRun to specify custom CloudWatch log group paths, and a RulesetName filter in ListDataQualityRulesetEvaluationRuns to filter evaluation runs by ruleset name.
  • api-change:imagebuilder: [botocore] The ImportDiskImage API now enforces a maximum character limit of 128 characters on the image name field.
  • api-change:lexv2-models: [botocore] Amazon Lex V2 introduces audio filler support for speech-to-speech bots. Configure melody or typing sounds that play during backend processing to reduce perceived latency and maintain a natural conversational experience for callers.
  • api-change:mwaa: [botocore] Amazon MWAA now supports a PublicAndPrivate webserver access mode. The Airflow web server is accessible over both public and private endpoints, enabling workers in VPCs without internet access to reach the Task API privately while retaining public access to the Airflow UI.
  • api-change:s3: [botocore] Validate outpost access point resource name
  • api-change:sagemaker: [botocore] Amazon SageMaker HyperPod now returns ImageVersionStatus in DescribeCluster, DescribeClusterNode, and ListClusterNodes responses, indicating whether cluster instances are running the latest available image version.
  • api-change:securityhub: [botocore] Release GenerateRecommendedPolicyV2 and GetRecommendedPolicyV2 APIs. This supports generating and retrieving policy recommendations to remediate unused permissions findings that are now being supported on Security Hub.

v1.43.4

Compare Source

======

  • api-change:cleanroomsml: [botocore] Increase max configurable output limits in the Clean Rooms ML configured model algorithm association resource.
  • api-change:cloudfront: [botocore] Adds support for tagging CloudFront Functions and KeyValueStores resources.
  • api-change:marketplace-agreement: [botocore] With this release, Agreements API provides a programmatic way to generate quotes, accept offers, track charges and entitlements, manage renewals and cancellations, and streamline operations entirely through APIs without navigating to the AWS Marketplace website or AWS Management Console.
  • api-change:mediatailor: [botocore] Added support for Monetization Functions. Monetization Functions let you enrich ad requests with external data and transform session parameters using JSONata expressions, without deploying custom infrastructure.
  • api-change:medical-imaging: [botocore] Add support for DICOM Json Metadata Override features in startDICOMImportJob API
  • api-change:opensearch: [botocore] Amazon OpenSearch Service now supports VPC egress, enabling outbound traffic from your OpenSearch domain to route privately through your VPC instead of the public internet.
  • api-change:route53domains: [botocore] This release adds the TLDInMaintenance exception.
  • api-change:sagemaker: [botocore] Adds support for ml.p5.4xlarge instance type for SageMaker Studio JupyterLab and CodeEditor apps for IAD (us-east-1), NRT (ap-northeast-1), BOM (ap-south-1), CGK (ap-southeast-3), GRU (sa-east-1), PDX (us-west-2), CMH (us-east-2).

v1.43.3

Compare Source

======

  • api-change:bedrock-agentcore-control: [botocore] Amazon Bedrock AgentCore gateways now support MCP Sessions and response streaming from MCP targets. Session timeouts can be set between 15 minutes and 8 hours, and response streaming enables forwarding stream events sent by MCP targets to gateway users.
  • api-change:ec2: [botocore] This feature allows customers to change the tunnel bandwidth on existing VPN connections using the ModifyVpnConnectionOptions API
  • api-change:geo-routes: [botocore] Added support for TravelTimeExceedsDriverWorkHours, ViolatedBlockedRoad, and ViolatedVehicleRestriction notice codes to the CalculateRoutes API response.
  • api-change:lex-models: [botocore] Lex V1 is deprecated, use Lex V2 instead
  • api-change:logs: [botocore] Adding an additional optional deliverySourceConfiguration field to PutDeliverySource API. This enables customers to pass service-specific configurations through IngestionHub such as tracing enablement or sampling rates that will be propagated to the source resource.
  • api-change:medialive: [botocore] Updates the type of the MediaLiveRouterOutputConnectionMap.
  • api-change:securityagent: [botocore] AWS Security Agent is adding a new target domain verification method for private VPC penetration testing. Additionally, the target domain resource will now have a verification status reason field to surface additional details about domain verification
  • api-change:vpc-lattice: [botocore] Amazon VPC Lattice now supports privately resolvable DNS resources

v1.43.2

Compare Source

======

  • api-change:appstream: [botocore] Amazon WorkSpaces Applications now enables AI agents to securely operate desktop applications. Administrators configure stacks to provide agents access to WorkSpaces. Agents can click, type, and take screenshots. Agents authenticate with AWS IAM credentials with activity logged in AWS CloudTrail.
  • api-change:cloudwatch: [botocore] This release adds tag support for CloudWatch Dashboards. The PutDashboard API now accepts a Tags parameter, allowing you to tag dashboards at creation time. Additionally, the TagResource, UntagResource, and ListTagsForResource APIs now support dashboard ARNs as resources.
  • api-change:entityresolution: [botocore] Add support for transitive matching in AWS Entity Resolution rule-based matching workflows. When enabled, records that match through different rules are grouped together into the same match group, allowing related records to be connected across rule levels.
  • api-change:iam: [botocore] Added guidance for CreateOpenIDConnectProvider to include multiple thumbprints when OIDC discovery and JWKS endpoints use different hosts or certificates
  • api-change:iot: [botocore] AWS IoT HTTP rule actions now support cross-topic batching, combining messages from different MQTT topics into single HTTP requests.
  • api-change:logs: [botocore] Adds support for filtering log groups by tags in the ListLogGroups API via the new logGroupTags parameter.
  • api-change:qconnect: [botocore] Added reasoning details, statusDescription, and timeToFirstTokenMs fields to the ListSpans response in Amazon Q in Connect to provide visibility into model thinking, error diagnostics, and inference latency metrics.
  • api-change:quicksight: [botocore] Add IdentityProviderCACertificatesBundleS3Uri for private CA certs with OAuth datasources. 256-char limit for FontFamily in themes. ControlTitleFormatText on all 13 filters. ControlTitleFontConfiguration. ContextRegion for cross-region identity context. Story,scenario in CreateCustomCapability API.

v1.43.1

Compare Source

======

  • api-change:bedrock-agentcore: [botocore] AgentCore Identity now supports on-behalf-of token exchange OAuth2. AgentCore Memory now supports metadata for LongTerm Memory Records.
  • api-change:bedrock-agentcore-control: [botocore] AgentCore Identity now supports on-behalf-of token exchange OAuth2. AgentCore Memory now supports metadata for LongTerm Memory Records.
  • api-change:datazone: [botocore] Adds support for asynchronous notebook runs
  • api-change:eks: [botocore] Vended logs update param for capability vended logs feature
  • api-change:kafka: [botocore] Adds support for ZookeeperAccess field to control the Client-Zookeeper connectivity.
  • api-change:observabilityadmin: [botocore] Observability Admin enablement launch for AWS Kafka, Bedrock Agent Core Workload Identity and OTel metric enablement.
  • api-change:payment-cryptography: [botocore] Adds support for resource-based policies on AWS Payment Cryptography keys, enabling cross-account key sharing. Also adds Multi-Party Approval (MPA) team association APIs for protecting sensitive import root public key operations.
  • api-change:route53globalresolver: [botocore] Adds support for regions in the UpdateGlobalResolver input.
  • api-change:sagemaker: [botocore] Add InstancePools support to Endpoint for flexible provisioning across a prioritized list of instance types. Add Specifications support to InferenceComponent for per-instance-type model configurations.
  • api-change:sso-admin: [botocore] Add InstanceArn and IdentityStoreArn in the response of CreateApplication API and IdentityStoreArn in the response of DescribeApplication API

v1.43.0

Compare Source

======

  • api-change:account: [botocore] Adds AccountState in the response for the GetAccountInformation API. Each state represents a specific phase in the account lifecycle. Use this information to manage account access, automate workflows, or trigger actions based on account state changes.
  • api-change:bedrock-agentcore: [botocore] Adds batch evaluation for running evaluators against multiple agent sessions with server-side orchestration, AI-powered recommendations for optimizing system prompts and tool descriptions, and AB testing with controlled traffic splitting and statistical significance reporting
  • api-change:bedrock-agentcore-control: [botocore] Adds configuration bundles for versioned, immutable agent configuration snapshots with branch-based lineage
  • api-change:cloudfront: [botocore] Amazon CloudFront now supports cache tag. Tag objects via response headers and invalidate all matching objects in a single request, replacing manual URL tracking and broad wildcards.
  • api-change:deadline: [botocore] Adds support for rtx-pro-server-6000 GPU accelerator for service-managed fleets.
  • api-change:ecr: [botocore] Removes support for registry policy V1
  • api-change:gamelift: [botocore] Amazon GameLift Servers adds a new DescribeContainerGroupPortMappings API for container fleets, making it easy to discover which connection ports map to your container ports without needing to remotely access the compute.
  • api-change:mediapackagev2: [botocore] This feature adds configuration for specifying SCTE marker handling and allow greater control over generated manifest and segment URIs
  • api-change:transfer: [botocore] This launch will increase the limits for customers to list the contents from the remote directories from 10k to 200k.
  • api-change:workspaces-web: [botocore] Allow admins to configure IPv6 ranges on IP Access Settings.
  • enhancement:awscrt: [botocore] Update awscrt version to 0.32.2
  • feature:Python: [botocore] End of support for Python 3.9
  • feature:Python: End of support for Python 3.9

Configuration

📅 Schedule: (in timezone US/Eastern)

  • Branch creation
    • "every weekend"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

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.


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

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

@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented May 2, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: uv.lock
Command failed: uv lock --upgrade-package boto3
Using CPython 3.14.5 interpreter at: /opt/containerbase/tools/python/3.14.5/bin/python3
  × No solution found when resolving dependencies for split (markers:
  │ python_full_version == '3.14.*' and sys_platform == 'win32'):
  ╰─▶ Because only the following versions of aiobotocore are available:
          aiobotocore<=2.5.4
          aiobotocore==2.6.0
          aiobotocore==2.7.0
          aiobotocore==2.8.0
          aiobotocore==2.9.0
          aiobotocore==2.9.1
          aiobotocore==2.10.0
          aiobotocore==2.11.0
          aiobotocore==2.11.1
          aiobotocore==2.11.2
          aiobotocore==2.12.0
          aiobotocore==2.12.1
          aiobotocore==2.12.2
          aiobotocore==2.12.3
          aiobotocore==2.12.4
          aiobotocore==2.13.0
          aiobotocore==2.13.1
          aiobotocore==2.13.2
          aiobotocore==2.13.3
          aiobotocore==2.14.0
          aiobotocore==2.15.0
          aiobotocore==2.15.1
          aiobotocore==2.15.2
          aiobotocore==2.16.0
          aiobotocore==2.16.1
          aiobotocore==2.17.0
          aiobotocore==2.18.0
          aiobotocore>=2.19.0
      and aiobotocore>=2.5.4,<=2.6.0 depends on botocore>=1.31.17,<1.31.18,
      we can conclude that aiobotocore>=2.5.4,<2.7.0 depends on
      botocore>=1.31.17,<1.31.18.
      And because aiobotocore==2.7.0 depends on botocore>=1.31.16,<1.31.65 and
      botocore>=1.32.4,<1.33.2, we can conclude that aiobotocore>=2.5.4,<2.9.0
      depends on one of:
          botocore>=1.31.16,<1.31.65
          botocore>=1.32.4,<1.33.2

      And because aiobotocore>=2.9.0,<=2.9.1 depends on
      botocore>=1.33.2,<1.33.14 and botocore>=1.33.2,<1.34.23, we can conclude
      that aiobotocore>=2.5.4,<2.11.1 depends on one of:
          botocore>=1.31.16,<1.31.65
          botocore>=1.32.4,<1.34.23

      And because aiobotocore==2.11.1 depends on botocore>=1.33.2,<1.34.28
      and botocore>=1.33.2,<1.34.35, we can conclude that
      aiobotocore>=2.5.4,<2.12.0 depends on one of:
          botocore>=1.31.16,<1.31.65
          botocore>=1.32.4,<1.34.35

      And because aiobotocore>=2.12.0,<=2.12.2 depends on
      botocore>=1.34.41,<1.34.52 and botocore>=1.34.41,<1.34.70, we can
      conclude that aiobotocore>=2.5.4,<2.12.4 depends on one of:
          botocore>=1.31.16,<1.31.65
          botocore>=1.32.4,<1.34.35
          botocore>=1.34.41,<1.34.70

      And because aiobotocore>=2.12.4,<=2.13.0 depends on
      botocore>=1.34.70,<1.34.107 and botocore>=1.34.70,<1.34.132, we can
      conclude that aiobotocore>=2.5.4,<2.13.3 depends on one of:
          botocore>=1.31.16,<1.31.65
          botocore>=1.32.4,<1.34.35
          botocore>=1.34.41,<1.34.132

      And because aiobotocore==2.13.3 depends on botocore>=1.34.70,<1.34.163
      and botocore>=1.35.0,<1.35.8, we can conclude that
      aiobotocore>=2.5.4,<2.15.0 depends on one of:
          botocore>=1.31.16,<1.31.65
          botocore>=1.32.4,<1.34.35
          botocore>=1.34.41,<1.35.8

      And because aiobotocore==2.15.0 depends on botocore>=1.35.16,<1.35.17
      and botocore>=1.35.16,<1.35.24, we can conclude that
      aiobotocore>=2.5.4,<2.15.2 depends on one of:
          botocore>=1.31.16,<1.31.65
          botocore>=1.32.4,<1.34.35
          botocore>=1.34.41,<1.35.8
          botocore>=1.35.16,<1.35.24

      And because aiobotocore==2.15.2 depends on botocore>=1.35.16,<1.35.37
      and botocore>=1.35.74,<1.35.82, we can conclude that
      aiobotocore>=2.5.4,<2.16.1 depends on one of:
          botocore>=1.31.16,<1.31.65
          botocore>=1.32.4,<1.34.35
          botocore>=1.34.41,<1.35.8
          botocore>=1.35.16,<1.35.37
          botocore>=1.35.74,<1.35.82

      And because aiobotocore==2.16.1 depends on botocore>=1.35.74,<1.35.89
      and botocore>=1.35.74,<1.35.94, we can conclude that
      aiobotocore>=2.5.4,<2.18.0 depends on one of:
          botocore>=1.31.16,<1.31.65
          botocore>=1.32.4,<1.34.35
          botocore>=1.34.41,<1.35.8
          botocore>=1.35.16,<1.35.37
          botocore>=1.35.74,<1.35.94

      And because aiobotocore==2.18.0 depends on botocore>=1.36.0,<1.36.2 and
      botocore>=1.42.90,<1.43.1, we can conclude that all of:
          aiobotocore>=2.5.4,<2.19.0
          aiobotocore>=3.6.0
      depend on one of:
          botocore>=1.31.16,<1.31.65
          botocore>=1.32.4,<1.34.35
          botocore>=1.34.41,<1.35.8
          botocore>=1.35.16,<1.35.37
          botocore>=1.35.74,<1.35.94
          botocore>=1.36.0,<1.36.2
          botocore>=1.42.90,<1.43.1

      And because aiobotocore==3.5.0 depends on botocore>=1.42.90,<1.42.92 and
      botocore>=1.42.79,<1.42.85, we can conclude that all of:
          aiobotocore>=2.5.4,<2.19.0
          aiobotocore>=3.4.0
      depend on one of:
          botocore>=1.31.16,<1.31.65
          botocore>=1.32.4,<1.34.35
          botocore>=1.34.41,<1.35.8
          botocore>=1.35.16,<1.35.37
          botocore>=1.35.74,<1.35.94
          botocore>=1.36.0,<1.36.2
          botocore>=1.42.79,<1.42.85
          botocore>=1.42.90,<1.43.1

      And because aiobotocore==3.3.0 depends on botocore>=1.42.62,<1.42.71 and
      botocore>=1.42.53,<1.42.62, we can conclude that all of:
          aiobotocore>=2.5.4,<2.19.0
          aiobotocore>=3.2.1
      depend on one of:
          botocore>=1.31.16,<1.31.65
          botocore>=1.32.4,<1.34.35
          botocore>=1.34.41,<1.35.8
          botocore>=1.35.16,<1.35.37
          botocore>=1.35.74,<1.35.94
          botocore>=1.36.0,<1.36.2
          botocore>=1.42.53,<1.42.71
          botocore>=1.42.79,<1.42.85
          botocore>=1.42.90,<1.43.1
       (1)

      Because only the following versions of aiobotocore are available:
          aiobotocore<=2.19.0
          aiobotocore==2.20.0
          aiobotocore==2.21.0
          aiobotocore==2.21.1
          aiobotocore==2.22.0
          aiobotocore==2.23.0
          aiobotocore==2.23.1
          aiobotocore==2.23.2
          aiobotocore==2.24.0
          aiobotocore==2.24.1
          aiobotocore==2.24.2
          aiobotocore==2.24.3
          aiobotocore==2.25.0
          aiobotocore==2.25.1
          aiobotocore==2.25.2
          aiobotocore==2.26.0
          aiobotocore==3.0.0
          aiobotocore==3.1.0
          aiobotocore==3.1.1
          aiobotocore==3.1.2
          aiobotocore==3.1.3
          aiobotocore==3.2.0
          aiobotocore==3.2.1
          aiobotocore==3.3.0
          aiobotocore==3.4.0
          aiobotocore==3.5.0
          aiobotocore==3.6.0
          aiobotocore==3.7.0
      and aiobotocore==2.19.0 depends on botocore>=1.36.0,<1.36.4,
      we can conclude that aiobotocore>=2.19.0,<2.20.0 depends on
      botocore>=1.36.0,<1.36.4.
      And because aiobotocore==2.20.0 depends on botocore>=1.36.20,<1.36.24,
      we can conclude that aiobotocore>=2.19.0,<2.21.0 depends on one of:
          botocore>=1.36.0,<1.36.4
          botocore>=1.36.20,<1.36.24

      And because aiobotocore>=2.21.0,<=2.21.1 depends on
      botocore>=1.37.0,<1.37.2 and botocore>=1.37.2,<1.37.4, we can conclude
      that aiobotocore>=2.19.0,<2.23.0 depends on one of:
          botocore>=1.36.0,<1.36.4
          botocore>=1.36.20,<1.36.24
          botocore>=1.37.0,<1.37.4

      And because aiobotocore==2.23.0 depends on botocore>=1.38.23,<1.38.28
      and botocore>=1.38.40,<1.38.47, we can conclude that
      aiobotocore>=2.19.0,<2.23.2 depends on one of:
          botocore>=1.36.0,<1.36.4
          botocore>=1.36.20,<1.36.24
          botocore>=1.37.0,<1.37.4
          botocore>=1.38.23,<1.38.28
          botocore>=1.38.40,<1.38.47

      And because aiobotocore==2.23.2 depends on botocore>=1.39.7,<1.39.9
      and botocore>=1.39.9,<1.39.12, we can conclude that
      aiobotocore>=2.19.0,<2.24.2 depends on one of:
          botocore>=1.36.0,<1.36.4
          botocore>=1.36.20,<1.36.24
          botocore>=1.37.0,<1.37.4
          botocore>=1.38.23,<1.38.28
          botocore>=1.38.40,<1.38.47
          botocore>=1.39.7,<1.39.12

      And because aiobotocore==2.24.2 depends on botocore>=1.40.15,<1.40.19
      and botocore>=1.40.37,<1.40.46, we can conclude that
      aiobotocore>=2.19.0,<2.25.0 depends on one of:
          botocore>=1.36.0,<1.36.4
          botocore>=1.36.20,<1.36.24
          botocore>=1.37.0,<1.37.4
          botocore>=1.38.23,<1.38.28
          botocore>=1.38.40,<1.38.47
          botocore>=1.39.7,<1.39.12
          botocore>=1.40.15,<1.40.19
          botocore>=1.40.37,<1.40.46

      And because aiobotocore==2.25.0 depends on botocore>=1.40.46,<1.40.50
      and botocore>=1.40.46,<1.40.62, we can conclude that
      aiobotocore>=2.19.0,<2.25.2 depends on one of:
          botocore>=1.36.0,<1.36.4
          botocore>=1.36.20,<1.36.24
          botocore>=1.37.0,<1.37.4
          botocore>=1.38.23,<1.38.28
          botocore>=1.38.40,<1.38.47
          botocore>=1.39.7,<1.39.12
          botocore>=1.40.15,<1.40.19
          botocore>=1.40.37,<1.40.62

      And because aiobotocore==2.25.2 depends on botocore>=1.40.46,<1.40.71
      and botocore>=1.41.0,<1.41.6, we can conclude that
      aiobotocore>=2.19.0,<3.0.0 depends on one of:
          botocore>=1.36.0,<1.36.4
          botocore>=1.36.20,<1.36.24
          botocore>=1.37.0,<1.37.4
          botocore>=1.38.23,<1.38.28
          botocore>=1.38.40,<1.38.47
          botocore>=1.39.7,<1.39.12
          botocore>=1.40.15,<1.40.19
          botocore>=1.40.37,<1.40.71
          botocore>=1.41.0,<1.41.6

      And because aiobotocore==3.0.0 depends on botocore>=1.41.0,<1.42.6
      and botocore>=1.41.0,<1.42.20, we can conclude that
      aiobotocore>=2.19.0,<3.1.1 depends on one of:
          botocore>=1.36.0,<1.36.4
          botocore>=1.36.20,<1.36.24
          botocore>=1.37.0,<1.37.4
          botocore>=1.38.23,<1.38.28
          botocore>=1.38.40,<1.38.47
          botocore>=1.39.7,<1.39.12
          botocore>=1.40.15,<1.40.19
          botocore>=1.40.37,<1.40.71
          botocore>=1.41.0,<1.42.20

      And because aiobotocore==3.1.1 depends on botocore>=1.41.0,<1.42.31
      and botocore>=1.41.0,<1.42.43, we can conclude that
      aiobotocore>=2.19.0,<3.1.3 depends on one of:
          botocore>=1.36.0,<1.36.4
          botocore>=1.36.20,<1.36.24
          botocore>=1.37.0,<1.37.4
          botocore>=1.38.23,<1.38.28
          botocore>=1.38.40,<1.38.47
          botocore>=1.39.7,<1.39.12
          botocore>=1.40.15,<1.40.19
          botocore>=1.40.37,<1.40.71
          botocore>=1.41.0,<1.42.43

      And because aiobotocore==3.1.3 depends on botocore>=1.41.0,<1.42.50
      and botocore>=1.42.53,<1.42.56, we can conclude that
      aiobotocore>=2.19.0,<3.2.1 depends on one of:
          botocore>=1.36.0,<1.36.4
          botocore>=1.36.20,<1.36.24
          botocore>=1.37.0,<1.37.4
          botocore>=1.38.23,<1.38.28
          botocore>=1.38.40,<1.38.47
          botocore>=1.39.7,<1.39.12
          botocore>=1.40.15,<1.40.19
          botocore>=1.40.37,<1.40.71
          botocore>=1.41.0,<1.42.50
          botocore>=1.42.53,<1.42.56
       (2)
      And because we know from (1) that all of:
          aiobotocore>=2.5.4,<2.19.0
          aiobotocore>=3.2.1
      depend on one of:
          botocore>=1.31.16,<1.31.65
          botocore>=1.32.4,<1.34.35
          botocore>=1.34.41,<1.35.8
          botocore>=1.35.16,<1.35.37
          botocore>=1.35.74,<1.35.94
          botocore>=1.36.0,<1.36.2
          botocore>=1.42.53,<1.42.71
          botocore>=1.42.79,<1.42.85
          botocore>=1.42.90,<1.43.1
      we can conclude that aiobotocore>=2.5.4 depends on one of:
          botocore>=1.31.16,<1.31.65
          botocore>=1.32.4,<1.34.35
          botocore>=1.34.41,<1.35.8
          botocore>=1.35.16,<1.35.37
          botocore>=1.35.74,<1.35.94
          botocore>=1.36.0,<1.36.4
          botocore>=1.36.20,<1.36.24
          botocore>=1.37.0,<1.37.4
          botocore>=1.38.23,<1.38.28
          botocore>=1.38.40,<1.38.47
          botocore>=1.39.7,<1.39.12
          botocore>=1.40.15,<1.40.19
          botocore>=1.40.37,<1.40.71
          botocore>=1.41.0,<1.42.50
          botocore>=1.42.53,<1.42.71
          botocore>=1.42.79,<1.42.85
          botocore>=1.42.90,<1.43.1

      And because s3fs==2026.1.0 depends on aiobotocore>=2.5.4 and only the
      following versions of s3fs are available:
          s3fs<2026.0.0
          s3fs==2026.1.0
          s3fs==2026.2.0
          s3fs==2026.3.0
          s3fs==2026.4.0
      we can conclude that s3fs>=2026.0.0,<2026.2.0 depends on one of:
          botocore>=1.31.16,<1.31.65
          botocore>=1.32.4,<1.34.35
          botocore>=1.34.41,<1.35.8
          botocore>=1.35.16,<1.35.37
          botocore>=1.35.74,<1.35.94
          botocore>=1.36.0,<1.36.4
          botocore>=1.36.20,<1.36.24
          botocore>=1.37.0,<1.37.4
          botocore>=1.38.23,<1.38.28
          botocore>=1.38.40,<1.38.47
          botocore>=1.39.7,<1.39.12
          botocore>=1.40.15,<1.40.19
          botocore>=1.40.37,<1.40.71
          botocore>=1.41.0,<1.42.50
          botocore>=1.42.53,<1.42.71
          botocore>=1.42.79,<1.42.85
          botocore>=1.42.90,<1.43.1
       (3)

      Because aiobotocore>=3.6.0 depends on botocore>=1.42.90,<1.43.1 and
      botocore>=1.42.90,<1.42.92, we can conclude that aiobotocore>=3.5.0
      depends on botocore>=1.42.90,<1.43.1.
      And because aiobotocore==3.4.0 depends on botocore>=1.42.79,<1.42.85, we
      can conclude that aiobotocore>=3.4.0 depends on one of:
          botocore>=1.42.79,<1.42.85
          botocore>=1.42.90,<1.43.1

      And because aiobotocore==3.3.0 depends on botocore>=1.42.62,<1.42.71
      and botocore>=1.42.53,<1.42.62, we can conclude that aiobotocore>=3.2.1
      depends on one of:
          botocore>=1.42.53,<1.42.71
          botocore>=1.42.79,<1.42.85
          botocore>=1.42.90,<1.43.1

      And because we know from (2) that aiobotocore>=2.19.0,<3.2.1 depends on
      one of:
          botocore>=1.36.0,<1.36.4
          botocore>=1.36.20,<1.36.24
          botocore>=1.37.0,<1.37.4
          botocore>=1.38.23,<1.38.28
          botocore>=1.38.40,<1.38.47
          botocore>=1.39.7,<1.39.12
          botocore>=1.40.15,<1.40.19
          botocore>=1.40.37,<1.40.71
          botocore>=1.41.0,<1.42.50
          botocore>=1.42.53,<1.42.56
      we can conclude that aiobotocore>=2.19.0 depends on one of:
          botocore>=1.36.0,<1.36.4
          botocore>=1.36.20,<1.36.24
          botocore>=1.37.0,<1.37.4
          botocore>=1.38.23,<1.38.28
          botocore>=1.38.40,<1.38.47
          botocore>=1.39.7,<1.39.12
          botocore>=1.40.15,<1.40.19
          botocore>=1.40.37,<1.40.71
          botocore>=1.41.0,<1.42.50
          botocore>=1.42.53,<1.42.71
          botocore>=1.42.79,<1.42.85
          botocore>=1.42.90,<1.43.1

      And because s3fs>=2026.2.0 depends on aiobotocore>=2.19.0, we can
      conclude that s3fs>=2026.2.0 depends on one of:
          botocore>=1.36.0,<1.36.4
          botocore>=1.36.20,<1.36.24
          botocore>=1.37.0,<1.37.4
          botocore>=1.38.23,<1.38.28
          botocore>=1.38.40,<1.38.47
          botocore>=1.39.7,<1.39.12
          botocore>=1.40.15,<1.40.19
          botocore>=1.40.37,<1.40.71
          botocore>=1.41.0,<1.42.50
          botocore>=1.42.53,<1.42.71
          botocore>=1.42.79,<1.42.85
          botocore>=1.42.90,<1.43.1

      And because we know from (3) that s3fs>=2026.0.0,<2026.2.0 depends on
      one of:
          botocore>=1.31.16,<1.31.65
          botocore>=1.32.4,<1.34.35
          botocore>=1.34.41,<1.35.8
          botocore>=1.35.16,<1.35.37
          botocore>=1.35.74,<1.35.94
          botocore>=1.36.0,<1.36.4
          botocore>=1.36.20,<1.36.24
          botocore>=1.37.0,<1.37.4
          botocore>=1.38.23,<1.38.28
          botocore>=1.38.40,<1.38.47
          botocore>=1.39.7,<1.39.12
          botocore>=1.40.15,<1.40.19
          botocore>=1.40.37,<1.40.71
          botocore>=1.41.0,<1.42.50
          botocore>=1.42.53,<1.42.71
          botocore>=1.42.79,<1.42.85
          botocore>=1.42.90,<1.43.1
      we can conclude that s3fs>=2026.0.0 depends on one of:
          botocore>=1.31.16,<1.31.65
          botocore>=1.32.4,<1.34.35
          botocore>=1.34.41,<1.35.8
          botocore>=1.35.16,<1.35.37
          botocore>=1.35.74,<1.35.94
          botocore>=1.36.0,<1.36.4
          botocore>=1.36.20,<1.36.24
          botocore>=1.37.0,<1.37.4
          botocore>=1.38.23,<1.38.28
          botocore>=1.38.40,<1.38.47
          botocore>=1.39.7,<1.39.12
          botocore>=1.40.15,<1.40.19
          botocore>=1.40.37,<1.40.71
          botocore>=1.41.0,<1.42.50
          botocore>=1.42.53,<1.42.71
          botocore>=1.42.79,<1.42.85
          botocore>=1.42.90,<1.43.1

      And because boto3==1.43.13 depends on botocore>=1.43.13, we can conclude
      that boto3==1.43.13 and s3fs>=2026.0.0 are incompatible.
      And because only boto3<=1.43.13 is available and ol-orchestrate-lib
      depends on boto3>=1.43.13, we can conclude that ol-orchestrate-lib and
      s3fs>=2026.0.0 are incompatible.
      And because ol-orchestrate-lib depends on s3fs>=2026.0.0 and your
      workspace requires ol-orchestrate-lib, we can conclude that your
      workspace's requirements are unsatisfiable.

      hint: The resolution failed for an environment that is not the current
      one, consider limiting the environments with `tool.uv.environments`.

      hint: Pre-releases are available for `aiobotocore` in the requested
      range (e.g., 2.20.1.dev0), but pre-releases weren't enabled (try:
      `--prerelease=allow`)

@renovate renovate Bot force-pushed the renovate/boto3-1.x branch 5 times, most recently from 57373b6 to 07f0504 Compare May 4, 2026 23:32
@renovate renovate Bot changed the title Update dependency boto3 to ~=1.43.2 Update dependency boto3 to ~=1.43.3 May 4, 2026
@renovate renovate Bot force-pushed the renovate/boto3-1.x branch 3 times, most recently from 76f1fa5 to 4e50fa4 Compare May 5, 2026 23:32
@renovate renovate Bot changed the title Update dependency boto3 to ~=1.43.3 Update dependency boto3 to ~=1.43.4 May 5, 2026
@renovate renovate Bot force-pushed the renovate/boto3-1.x branch 2 times, most recently from ee0edd8 to 8defe99 Compare May 6, 2026 23:04
@renovate renovate Bot changed the title Update dependency boto3 to ~=1.43.4 Update dependency boto3 to ~=1.43.5 May 6, 2026
@renovate renovate Bot force-pushed the renovate/boto3-1.x branch 5 times, most recently from 9ae34e4 to 3b30fb6 Compare May 7, 2026 21:07
@renovate renovate Bot changed the title Update dependency boto3 to ~=1.43.5 Update dependency boto3 to ~=1.43.6 May 7, 2026
@renovate renovate Bot force-pushed the renovate/boto3-1.x branch 8 times, most recently from c90fa31 to 57bf0f3 Compare May 12, 2026 18:53
@renovate renovate Bot changed the title Update dependency boto3 to ~=1.43.6 Update dependency boto3 to ~=1.43.6 - autoclosed May 12, 2026
@renovate renovate Bot changed the title Update dependency boto3 to ~=1.43.6 - autoclosed Update dependency boto3 to ~=1.43.9 May 16, 2026
@renovate renovate Bot reopened this May 16, 2026
@renovate renovate Bot force-pushed the renovate/boto3-1.x branch 7 times, most recently from 158b03c to cc1407e Compare May 18, 2026 22:11
@renovate renovate Bot changed the title Update dependency boto3 to ~=1.43.9 Update dependency boto3 to ~=1.43.10 May 18, 2026
@renovate renovate Bot force-pushed the renovate/boto3-1.x branch 6 times, most recently from ea212bc to a24d6d7 Compare May 19, 2026 20:13
@renovate renovate Bot changed the title Update dependency boto3 to ~=1.43.10 Update dependency boto3 to ~=1.43.11 May 19, 2026
@renovate renovate Bot force-pushed the renovate/boto3-1.x branch 4 times, most recently from 235ab93 to 5879093 Compare May 20, 2026 22:50
@renovate renovate Bot changed the title Update dependency boto3 to ~=1.43.11 Update dependency boto3 to ~=1.43.12 May 20, 2026
@renovate renovate Bot force-pushed the renovate/boto3-1.x branch 5 times, most recently from a7f237f to 54949ea Compare May 21, 2026 21:28
@renovate renovate Bot force-pushed the renovate/boto3-1.x branch from 54949ea to 963f334 Compare May 21, 2026 21:55
@renovate renovate Bot changed the title Update dependency boto3 to ~=1.43.12 Update dependency boto3 to ~=1.43.13 May 21, 2026
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