chore(deps): update all patch dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence	Type	Update	Pending
boto3	==1.40.64 -> ==1.40.69				patch	1.40.74 (+4)
coverage	==7.11.0 -> ==7.11.3				patch
github.com/cds-snc/terraform-modules	v10.8.4 -> v10.8.6			module	patch

Review

• Updates have been tested and work
• If updates are AWS related, versions match the infrastructure (e.g. Lambda runtime, database, etc.)

---

Release Notes

boto/boto3 (boto3)

v1.40.69

Compare Source

=======

• api-change:controltower: [botocore] Added Parent Identifier support to ListEnabledControls and GetEnabledControl API. Implemented RemediationType support for Landing Zone operations: CreateLandingZone, UpdateLandingZone and GetLandingZone APIs
• api-change:ec2: [botocore] Adds PrivateDnsPreference and PrivateDnsSpecifiedDomains to control private DNS resolution for resource and service network VPC endpoints and IpamScopeExternalAuthorityConfiguration to integrate Amazon VPC IPAM with a third-party IPAM service
• api-change:kms: [botocore] Added support for new ECC_NIST_EDWARDS25519 AWS KMS key spec
• api-change:opensearch: [botocore] This release introduces the Default Application feature, allowing users to set, change, or unset a preferred OpenSearch UI application on a per-region basis for a streamlined and consistent user experience.
• api-change:vpc-lattice: [botocore] Amazon VPC Lattice now supports custom domain name for resource configurations

v1.40.68

Compare Source

=======

• api-change:accessanalyzer: [botocore] New field totalActiveErrors added to getFindingsStatistics response.
• api-change:backup: [botocore] AWS Backup now supports customer-managed keys (CMK) for logically air-gapped vaults, enabling customers to maintain full control over their encryption key lifecycle. This feature helps organizations meet specific internal governance requirements or external regulatory compliance standards.
• api-change:connect: [botocore] Added support for Conditional Questions in Evaluation Forms. Introduced Auto Evaluation capability for Evaluation Forms and Contact Evaluations. Added new API operations: SearchEvaluationForms and SearchContactEvaluations.
• api-change:ec2: [botocore] Add Amazon EC2 R8a instance types
• api-change:gamelift: [botocore] Amazon GameLift Servers now supports game builds that use the Windows 2022 operating system.
• api-change:identitystore: [botocore] IdentityStore API: added new KMSExceptionReason fields to the Exception object; added multiple new fields to the User APIs - UserStatus, Birthdate, Website and Photos; added multiple new metadata fields for User, Groups and Membership APIs - CreatedAt, CreatedBy, UpdatedAt and UpdatedBy.
• api-change:quicksight: [botocore] Support for New Data Prep Experience
• api-change:s3tables: [botocore] Adds support for tagging APIs for S3 Tables
• api-change:s3vectors: [botocore] Amazon S3 Vectors provides cost-effective, elastic, and durable vector storage for queries based on semantic meaning and similarity.
• api-change:sagemaker: [botocore] Added NodeProvisioningMode parameter to UpdateCluster API to determine how instance provisioning is handled during cluster operations; in Continuous mode. Added VpcId field in UpdateDomain request for SageMaker Unified Studio domains with no VPC to add a customer VPC.
• api-change:ssm: [botocore] Provides NoLongerSupportedException error message

v1.40.67

Compare Source

=======

• api-change:cloudfront: [botocore] This release adds new and updated API operations. You can now use the IpAddressType field to specify either ipv4 or dualstack for your Anycast static IP list. You can also enable cross-account resource sharing to share your VPC origins with other AWS accounts
• api-change:datazone: [botocore] Added support for Project Resource Tags
• api-change:ec2: [botocore] This release adds AvailabilityZoneId support for DescribeFastSnapshotRestores, DisableFastSnapshotRestores, and EnableFastSnapshotRestores APIs.
• api-change:endpoint-rules: [botocore] Update endpoint-rules client to latest version
• api-change:fsx: [botocore] Amazon FSx now enables secure management of Active Directory credentials through AWS Secrets Manager integration. Customers can use Secret ARNs instead of direct credentials when joining resources to Active Directory domains.
• api-change:groundstation: [botocore] Introduce CreateDataflowEndpointGroupV2 action
• api-change:s3: [botocore] Launch IPv6 dual-stack support for S3 Express
• api-change:sagemaker: [botocore] Add new fields in SageMaker Hyperpod DescribeCluster API response: TargetStateCount, SoftwareUpdateStatus and ActiveSoftwareDeploymentConfig to provide AMI update progress visibility .

v1.40.66

Compare Source

=======

• api-change:pinpoint-sms-voice-v2: [botocore] This release adds support for the CarrierLookup API, which returns information about a destination phone number including if the number is valid, the carrier, and more.

v1.40.65

Compare Source

=======

• api-change:bedrock-agentcore-control: [botocore] Adds support for direct code deploy with CreateAgentRuntime and UpdateAgentRuntime
• api-change:budgets: [botocore] Fix the AWS Budgets endpoint for the aws-eusc partition.
• api-change:ec2: [botocore] Add Amazon EC2 trn2.3xlarge instance type.
• api-change:ecs: [botocore] Documentation-only update for LINEAR and CANARY deployment strategies.
• api-change:endpoint-rules: [botocore] Update endpoint-rules client to latest version
• api-change:kinesis: [botocore] Adds support for MinimumThroughputBillingCommitment with new UpdateAccountSettings API. Adds support to configure warm throughput for on-demand streams in new UpdateStreamWarmThroughput API and existing CreateStream API and UpdateStreamMode API.

coveragepy/coveragepy (coverage)

v7.11.3

Compare Source

• Fix: the 7.11.1 changes meant that conflicts between a requested measurement
  core and other settings would raise an error. This was a breaking change from
  previous behavior, as reported in issue 2076_ and issue 2078_.

  The previous behavior has been restored: when the requested core conflicts
  with other settings, another core is used instead, and a warning is issued.

• For contributors: the repo has moved from Ned's nedbat GitHub account_ to
  the coveragepy GitHub organization_. The default branch has changed from
  master to main.

.. _issue 2076: #​2076
.. _issue 2078: #​2078
.. _nedbat GitHub account: https://github.com/nedbat
.. _coveragepy GitHub organization: https://github.com/coveragepy

.. _changes_7-11-2:

v7.11.2

Compare Source

• Fix: using the "sysmon" measurement core in 7.11.1, if Python code was
  claimed to come from a non-Python file, a NotPython exception could be
  raised. This could happen for example with Jinja templates compiled to
  Python, as reported in issue 2077_. This is now fixed.

• Doc: corrected the first entry in the 7.11.1 changelog.

.. _issue 2077: #​2077

.. _changes_7-11-1:

v7.11.1

Compare Source

• Fix: some chanages to details of how the measurement core is chosen, and how
  conflicting settings are handled. The "sysmon" core cannot be used with some
  conurrency settings, with dynamic context, and in Python 3.12/3.13, with
  branch measurement.

  • If the core is not specified and defaults to "sysmon" (Python 3.14+), but
    other settings conflict with sysmon, then the "ctrace" core will be used
    instead with no warning. For concurrency conflicts, this used to produce an
    error, as described in issue 2064_.

  • If the "sysmon" core is explicitly requested in your configuration, but
    other settings conflict, an error is now raised. This used to produce a
    warning.

• Fix: some multi-line case clauses or for loops (and probably other
  constructs) could cause incorrect claims of missing branches with the
  sys.monitoring core, as described in issue 2070_. This is now fixed.

• Fix: when running in pytest under coverage, a breakpoint() would stop in
  the wrong frame, one level down from where it should, as described in issue 1420_. This was due to a coverage change in v6.4.1 that seemed to give a
  slight performance improvement, but I couldn't reproduce the performance
  gain, so it's been reverted, fixing the debugger problem.

• A new debug option --debug=core shows which core is in use and why.

• Split sqlite debugging information out of the sys :ref:coverage debug <cmd_debug> and :ref:cmd_run_debug options since it's bulky and not
  very useful.

• Updated the :ref:howitworks page to better describe the three different
  measurement cores.

.. _issue 1420: #​1420
.. _issue 2064: #​2064
.. _issue 2070: #​2070

.. _changes_7-11-0:

cds-snc/terraform-modules (github.com/cds-snc/terraform-modules)

v10.8.6

Compare Source

What's Changed

• feat: add custom assume role policies by @​patheard in #​758
• fix: variable naming to be consistent by @​patheard in #​759

Full Changelog: cds-snc/terraform-modules@v10.8.5...v10.8.6

v10.8.5

Compare Source

What's Changed

• chore(deps): update all patch dependencies by @​renovate[bot] in #​756
• fix: allow lambda assume role policies by @​patheard in #​757

Full Changelog: cds-snc/terraform-modules@v10.8.4...v10.8.5

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone America/Montreal, 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.

---

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

---

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