chore(deps): update dependency boto3 to v1.42.51

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
boto3	==1.42.46 → ==1.42.51

---

Release Notes

boto/boto3 (boto3)

v1.42.51

=======

• api-change:ec2: [botocore] Add Operator field to CreatePlacementGroup and DescribePlacementGroup APIs.
• api-change:evidently: [botocore] The evidently client has been removed following the deprecation of the service.
• api-change:grafana: [botocore] This release updates Amazon Managed Grafana's APIs to support customer managed KMS keys.
• api-change:iotanalytics: [botocore] The iotanalytics client has been removed following the deprecation of the service.
• api-change:rds: [botocore] Adds support for the StorageEncryptionType field to specify encryption type for DB clusters, DB instances, snapshots, automated backups, and global clusters.
• api-change:workspaces-web: [botocore] Adds support for branding customization without requiring a custom wallpaper.

v1.42.50

Compare Source

=======

• api-change:arc-region-switch: [botocore] Clarify documentation on ARC Region Switch start-plan-execution operation
• api-change:ec2: [botocore] Documentation updates for EC2 Secondary Networks
• api-change:ecr: [botocore] Adds support for enabling blob mounting, and removes support for Clair based image scanning
• api-change:kafka: [botocore] Amazon MSK now supports dual-stack connectivity (IPv4 and IPv6) for existing MSK clusters. You can enable dual-stack on existing clusters by specifying the NetworkType parameter in updateConnectivity API.
• api-change:kms: [botocore] Added support for Decrypt and ReEncrypt API's to use dry run feature without ciphertext for authorization validation
• api-change:qconnect: [botocore] Update MessageType enum to include missing types.

v1.42.49

Compare Source

=======

• api-change:cloudwatch: [botocore] Adding new evaluation states that provides information about the alarm evaluation process. Evaluation error Indicates configuration errors in alarm setup that require review and correction. Evaluation failure Indicates temporary CloudWatch issues.
• api-change:connect: [botocore] API release for headerr notifications in the admin website. APIs allow customers to publish brief messages (including URLs) to a specified audience, and a new header icon will indicate when unread messages are available.
• api-change:ec2: [botocore] This release adds geography information to EC2 region and availability zone APIs. DescribeRegions now includes a Geography field, while DescribeAvailabilityZones includes both Geography and SubGeography fields, enabling better geographic classification for AWS regions and zones.
• api-change:inspector2: [botocore] Added .Net 10 (dotnet10) and Node 24.x (node24.x) runtime support for lambda package scanning
• api-change:sagemaker: [botocore] Enable g7e instance type support for SageMaker Processing, and enable single file configuration provisioning for HyperPod Slurm, where customers have the option to use HyperPod API to provide the provisioning parameters.
• enhancement:AWSCRT: [botocore] Update awscrt version to 0.31.2

v1.42.48

Compare Source

=======

• api-change:ec2: [botocore] Launching nested virtualization. This feature allows you to run nested VMs inside virtual (non-bare metal) EC2 instances.

v1.42.47

Compare Source

=======

• api-change:batch: [botocore] Add support for listing jobs by share identifier and getting snapshots of active capacity utilization by job queue and share.
• api-change:ec2: [botocore] R8i instances powered by custom Intel Xeon 6 processors available only on AWS with sustained all-core 3.9 GHz turbo frequency
• api-change:eks: [botocore] This release adds support for Windows Server 2025 in Amazon EKS Managed Node Groups.
• api-change:kafkaconnect: [botocore] Support configurable upper limits on task count during autoscaling operations via maxAutoscalingTaskCount parameter.
• api-change:s3tables: [botocore] S3 Tables now supports setting partition specifications and sort orders on tables. Partition specs allow users to define how data is organized using transform functions. Sort order configurations enable users to specify sort directions and null ordering preferences for optimized data layout.

---

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.