chore(deps): Update testing-tools - #1734
Merged
Merged
Conversation
github-actions
Bot
added
dependencies
mchmarny
approved these changes
Jul 13, 2026
Contributor
Author
Coverage Report ✅
Coverage BadgeNo Go source files changed in this PR. |
mohityadav8
pushed a commit
to mohityadav8/aicr
that referenced
this pull request
Jul 14, 2026
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Mark Chmarny <mchmarny@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.45.41→1.45.451.45.46v2.9.0→v2.9.1v4.2.2→v4.2.31.3.72→1.4.1v0.80.0→v0.81.0Warning
Some dependencies could not be looked up. Check the warning logs for more information.
Release Notes
aws/aws-cli (awscli)
v1.45.45Compare Source
=======
connect: Amazon Connect - Added DeleteContactData API to support PII deletion of customer endpoint, additional email recipients and email subject.ec2: Added support for additional override parameters in CreateFleet, including LaunchTemplateSpecificationUserData, KeyName, IamInstanceProfile, and MetadataOptions. The CreateFleet response now also includes SubnetId, AvailabilityZone, and AvailabilityZoneId for launched instances.guardduty: Adding "AI Analyst" enum value for detectorivs: adds support for AWS IVS ad configuration APIs to allow for a postRollConfiguration object on the ad configuration resourcesynthetics: CloudWatch Synthetics adds support for customer managed KMS keys for canary environment variables. Customers can now encrypt their canary's Lambda function environment variables at rest using their own AWS KMS key, providing additional control over data protection.v1.45.44Compare Source
=======
endpoint-rules: Update endpoint-rules command to latest versionsignin: Adds support for OAuth 2.0 token operations in AWS Sign-In, CreateOAuth2TokenWithIAM (client credentials flow), IntrospectOAuth2TokenWithIAM (token inspection), and RevokeOAuth2TokenWithIAM (token revocation).v1.45.43Compare Source
=======
appconfig: Update ExperimentRun APIs to support ConflictExceptions.bedrock-agentcore-control: AgentCore Gateway now supports mapping allowed scopes to separate advertised scopes on the inbound authorizer.ec2: Replace Root Volume now supports a VolumeId parameter. This allows the customer to pass in a pre-prepared volume as the target root volume for an RRV workflow.ecs: Amazon ECS now automatically detects the correct CPU architecture for Express Mode services.geo-places: Added AddressNamesMode, AddressNameTranslations, MobilityMode, PostalCodeMode, SecondaryAddresses, and DriveThrough features across Places V2 APIs to support address name formatting, multilingual translations, travel-aware search, multi-city postal codes, and unit-level address resolution.iotwireless: Default session downlink transmission parameters have been added to the existing Multicast Group APIs. Explicit transmission parameters are no longer required when starting a multicast session during the FUOTA procedure.resiliencehubv2: Next Generation Resilience Hub now supports filtering and sorting failure mode assessments, resource type filtering in ListResources, cross-region and cross-account topology edges, data recovery achievability status, and more granular dependency discovery progress tracking.v1.45.42Compare Source
=======
config: Added support for connecting AWS Config to third-party cloud service providers. New APIs include PutConnector, GetConnector, DeleteConnector, and ListConnectors for managing connectors, and PutThirdPartyServiceLinkedConfigurationRecorder for creating third-party service-linked recorders.connect: Adds support for CreateAuthCode and DeleteSession APIs.ec2: This launch surfaces the public SSM parameter associated with public AMIs in the AMI metadata.endpoint-rules: Update endpoint-rules command to latest versioninspector2: This release extends vulnerability management to Azure VM, container registries and function apps. Adds support for per-member-account scan configuration settings.lambda: AWS Lambda Durable Functions now supports customer managed KMS keys. This allows customers to configure a KMS key in Durable Config to have all their durable execution data encrypted.marketplace-catalog: This release enhances the ListEntities API to support ResellerRole filter for ResaleAuthorization entity.meteringmarketplace: The usage reporting window for the BatchMeterUsage API has been extended from 6 hours to 24 hours. Sellers can now submit usage records for up to 24 hours after a metered event occurs. The existing 6-hour grace period at the end of a billing cycle still applies.partnercentral-revenue-measurement: Add support for AWS Partner Central Revenue Measurement API for creating, managing, and tracking revenue attributions and marketplace revenue share allocations.route53globalresolver: Adds ListSharedDNSViews operation to list all DNS Views shared with caller using AWS Resource Access Manager. Also updates ListHostedZoneAssociations operation so that resource ARN param is optional, allowing caller to list all HostedZoneAssociations in account.securityhub: release SecurityHub MultiCloud integration with Azuressm: Adding SSM Cloud Connector to support Azure Virtual Machines onboarding to AWS Systems Managerfluxcd/flux2 (fluxcd/flux2)
v2.9.1Compare Source
Highlights
Flux v2.9.1 is a patch release. The main fix, applied across all controllers, disables Flux variable substitution on the Flux CRDs by annotating them with
kustomize.toolkit.fluxcd.io/substitute: disabled, so that Kustomizations with post-build substitution enabled no longer corrupt the CRD schemas when they contain${...}sequences. Users are encouraged to upgrade for the best experience.ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.
Fixes:
${...}sequences (all controllers).inifile decryption (kustomize-controller)<resource> is invalid(kustomize-controller)Improvements:
Components changelog
CLI changelog
Full Changelog: fluxcd/flux2@v2.9.0...v2.9.1
helm/helm (helm/helm)
v4.2.3: Helm v4.2.3Compare Source
Helm v4.2.3 is a patch release. Users are encouraged to upgrade for the best experience.
The community keeps growing, and we'd love to see you there!
Installation and Upgrading
Download Helm v4.2.3. The common platform binaries are here:
The Quickstart Guide will get you going from there. For upgrade instructions or detailed installation notes, check the install guide. You can also use a script to install on any system with
bash.What's Next
Changelog
43e8b7f(Terry Howe)ministackorg/ministack (ministackorg/ministack)
v1.4.1Compare Source
Added
/etc/rancher/k3s/registries.yamlthat mirrors the cluster's ECR registry hostname (<account>.dkr.ecr.<region>.amazonaws.com) to the MiniStack gateway, sokubectl run --image <account>.dkr.ecr.<region>.amazonaws.com/repo:tagpulls an image you pushed to local ECR — no manual registry wiring. The mirror endpoint is MiniStack's own address on the shared Docker network when one is detected, andhost.docker.internal(added to the k3s container viahost-gateway) when MiniStack runs on the host. Verified end-to-end: image pushed to local ECR, pod pulled and reachedRunning. Reported by @L3337.mysql:8tag, which had started silently booting MySQL 8.4 for Aurora MySQL 8.0 test cases.DescribeDBEngineVersionsreturns the full creatable Aurora MySQL catalog with correct per-family parameter groups — including the new8.4.mysql_aurora.8.4.7/aurora-mysql8.4(GA 2026-05-21) — an explicitEngineVersionnot in the catalog is rejected with the AWS error shape, andaurora-mysql8.4parameter-group defaults omitskip-character-set-client-handshake(removed in MySQL 8.4) while older families keep it. The default Aurora MySQL version moves from the no-longer-creatable8.0.mysql_aurora.3.03.0to8.0.mysql_aurora.3.10.3. Contributed by @Areson.Changed
DockerfileAlpine andDockerfile.fullDebian) move frompython:3.12topython:3.13, clearing the CPython 3.12 interpreter CVEs flagged by image scanners; CI now runs the test suite on 3.13 to match the shipped interpreter.Dockerfile.fullalso runsapt-get upgradeso Debian base packages pick up security patches on every rebuild, as its comment always claimed and as the Alpine image already did. Contributed by @scottschreckengaust.Fixed
provided.*invocations no longer fail withETXTBSY("Text file busy") — each invocation extracted the function zip into its own temp directory and exec'd thebootstrapbinary from it; while one thread still held the extraction's write descriptor, another thread's process spawn let the child inherit it, and executing the binary failed withETXTBSY(a classic CPython fork/exec race). Extraction is now content-addressed — one shared read-only directory per code sha256, matching real Lambda's read-only/var/task— and spawns are serialized against extraction so the race cannot occur. Reported by @crestonbunch.provided.*runtime env restoresAWS_LAMBDA_FUNCTION_MEMORY_SIZE,AWS_LAMBDA_FUNCTION_VERSION, andAWS_LAMBDA_LOG_STREAM_NAME— 1.4.0's reserved-name filtering stripped these from the user environment, and the provided-runtime executor (unlike the container, local, and warm-worker paths) never re-injected them from the function config, so the Rustlambda_runtimecrate — which requiresAWS_LAMBDA_FUNCTION_MEMORY_SIZE— crashed on startup. All three are now set from the function configuration, matching the other executors and real AWS. Reported by @crestonbunch.messageAttributesin camelCase — records forwarded to functions carried the PascalCase inner keys SQS uses on the wire (StringValue/DataType/BinaryValue), but real Lambda re-serializes them to camelCase (stringValue/dataType/…) before invoking. Typed handler bindings — e.g. Java'sSQSEvent.MessageAttribute, which Jackson populates case-strictly — saw all-null attributes and failed on messages whose attributes were set correctly. The ESM now performs the same camelCase transformation as AWS at the delivery boundary; the SQS API surface itself is unchanged. Reported by @w-zx.versionIdsurvives payload persistence to a volume — withS3_PERSIST=1, the on-disk.meta.jsonsidecar never recorded the object'sversion_id, and all four write paths (PutObject, POST upload, CopyObject, CompleteMultipartUpload) persisted the sidecar before the version id was assigned — so after a restart, GET/HEAD returned nox-amz-version-idfor objects on the volume. The sidecar now stores the version id and is written after version assignment, so the current version id of every object survives restarts. (Historical version data is still memory-only; full version-history persistence is tracked separately.) Reported by @adzcodemi.ListUsersparses quoted attribute names inFilter— the filter parser only matched unquoted attribute names, but AWS's documented syntax also accepts the quoted form ("email" = "value"— used in AWS's own API-reference sample request), and on any parse failure MiniStack silently returned all users. Both forms now parse (including the docs' no-space"email"^="value"shape), and an unparseable filter logs a warning. Contributed by @kjdev.v1.4.0Compare Source
Added
X-Amz-Credentialquery parameter), so two clients pointed at different regions see fully independent state, matching real AWS. Region-isolated in this release: AppConfig, Bedrock, Bedrock Agent, Bedrock Agent Runtime, Bedrock Runtime, CloudWatch, CloudWatch Logs, DynamoDB (tables, metadata, and Streams), Lambda (functions, event source mappings, durable executions), MSK, RDS, S3 Tables, Secrets Manager, SQS, SSM Parameter Store, and Step Functions. Cross-resource references resolve in the referenced ARN's own account and region (SNS→SQS fanout, EventBridge targets, ESM sources), background workers (event source pollers, the EventBridge scheduler tick, durable-function resume) re-scope to each resource's tenant, and ARNs are parsed and validated everywhere — cross-region references that real AWS rejects now return the same errors AWS returns. Persisted state moves to an on-disk format v2 with a version stamp (a newer-format file is refused instead of mis-parsed on downgrade); legacy account-scoped state files load and migrate automatically, recovering each record's region from its stored ARNs. Services not listed above keep sharing state across regions within an account, exactly as in 1.3.x — region isolation for them lands in subsequent releases. Note forPERSIST_STATEusers: legacy records that carry no ARN migrate to the default region (MINISTACK_REGION), so pre-1.4 state created with a client region different fromMINISTACK_REGIONin a non-ARN service reads back under the default region. Contributed by @Areson.Converse,ConverseStream,InvokeModel,InvokeModelWithResponseStreamwith real eventstream wire format,ApplyGuardrail, and async invokes — deterministic family-aware mock responses selected by model ID prefix for Anthropic, Titan, Nova, Llama, Mistral, Cohere, and AI21 shapes), bedrock-agent (72 operations — agents, knowledge bases, data sources, ingestion jobs, flows, prompts, tags), and bedrock-agent-runtime (31 operations —InvokeAgent,Retrieve/RetrieveAndGenerate, reranking, sessions, flow executions, prompt optimization). Led by @dcabib.CreateCluster,ListClusters,DescribeCluster,DeleteCluster,ListNodes), configurations with revisions, SCRAM secret association, and tagging.GetBootstrapBrokershonorsMINISTACK_MSK_BOOTSTRAPso clients route to a real broker you bring (Redpanda, Kafka, KRaft) while the control plane stays emulated; the Kafka wire protocol itself is not emulated.zarf-dev/zarf (zarf-dev/zarf)
v0.81.0Compare Source
⚠ BREAKING CHANGES
Features
Bug Fixes
What's Changed
🚀 Updates
Full Changelog: zarf-dev/zarf@v0.81.0-rc1...v0.81.0
Verifying Init Packages
The init packages in this release are signed with keyless Sigstore signing. Verify with:
amd64:
arm64:
See RELEASES.md for details.
Configuration
📅 Schedule: (UTC)
🚦 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 has been generated by Mend Renovate.