Skip to content

chore(deps): update dependency boto3 to v1.43.11#225

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

chore(deps): update dependency boto3 to v1.43.11#225
dreadnode-renovate-bot[bot] wants to merge 1 commit into
mainfrom
renovate/boto3-1.x

Conversation

@dreadnode-renovate-bot
Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
boto3 ==1.43.9==1.43.11 age confidence

Release Notes

boto/boto3 (boto3)

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

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Enabled.

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 has been generated by Mend Renovate.

| datasource | package | from   | to      |
| ---------- | ------- | ------ | ------- |
| pypi       | boto3   | 1.43.9 | 1.43.11 |
@dreadnode-renovate-bot dreadnode-renovate-bot Bot added this pull request to the merge queue May 20, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to a conflict with the base branch May 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants