fix(deps): update all non-major dependencies#186
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
Conversation
Pull Request Test Coverage Report for Build 19743226991Details
💛 - Coveralls |
0ce9187 to
f982391
Compare
8d4f733 to
639392b
Compare
835f819 to
6e9cf42
Compare
8db7bcb to
a18bb9e
Compare
c745721 to
0afdcef
Compare
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
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:
==25.12.0→==25.12.1==2.19.5→==2.20.5==25.11.1→==25.12.2==25.11.1→==25.12.2>=0.9.18,<0.10→>=0.11,<0.12==0.9.21→==0.11.0==1.106.0→==1.109.0==2.17.0→==2.18.0==1.42.30→==1.43.2==1.42.30→==1.43.2==2026.1.4→==2026.4.22==1.41.0→==1.50.1==1.41.0→==1.50.1==3.4.4→==3.4.7==8.3.0→==8.3.3==7.13.1→==7.13.5==4.0.2→==4.1.0==3.3.0→==3.4.0==0.21.2→==0.22.4==3.20.3→==3.29.0==4.61.1→==4.62.1==1.0.0→==1.0.1==2.6.16→==2.6.19==3.11→==3.13==1.4.1→==1.5.0==8.7.1→==8.9.0==9.7.0→==9.13.0==9.7.0→==9.13.0==0.19.2→==0.20.0==1.0.1→==1.1.0==3.0.0→==3.1.1==0.3.4→==0.4.6==1.4.9→==1.5.0==3.10.8→==3.10.9==1.3.0→==1.4.1==1.18.2→==1.20.2==1.18.2→==1.20.2==2.15.0→==2.20.0==2.4.1→==2.4.4==0.22.0→==0.23.1==0.6.3→==0.9.0==0.7.2→==0.8.5==0.8.5→==0.8.7==0.4.4→==0.5.0==1.0.3→==1.1.1==4.5.1→==4.9.6==6.5.2→==6.7.0==1.37.1→==1.40.1==1.37.1→==1.40.1==4.5.0→==4.6.0==4.5.0→==4.6.0==2.12.5→==2.13.3==2.41.5→==2.46.3==3.3.1→==3.3.23.11→3.14==0.4.0→==0.4.1==0.36.2→==0.37.0==2026.1.15→==2026.4.4==0.16.0→==0.17.0==1.17.0→==1.17.1==80.9.0→==80.10.2==3.5.2→==3.10.2==3.5.2→==3.10.2==3.0.2→==3.1.0==3.0.2→==3.1.0==3.4.2→==3.5.0==3.4.2→==3.5.0==2.4.0→==2.4.1==4.67.1→==4.67.3==20.36.1→==20.39.1==0.2.14→==0.6.0==1.0.2→==1.0.4==1.37.1→==1.38.0==1.37.1→==1.38.0==3.23.0→==3.23.1==1.17.0→==1.24.1==1.17.0→==1.24.1Release Notes
ansible/ansible-compat (ansible-compat)
v25.12.1Compare Source
Fixes
Maintenance
ansible/ansible-lint (ansible-lint)
v25.12.2Compare Source
Fixes
Maintenance
v25.12.1Compare Source
Features
Fixes
Maintenance
v25.12.0Compare Source
Maintenance
manzt/anywidget (anywidget)
v0.11.0Compare Source
This release implements the widget composition RFC shared earlier this year. All changes are additive: existing widgets keep working without modification.
Background
For the past year, anywidget has predominantly been in maintenance mode. The library works, and the community has been expanding on both ends (more host platforms and more widgets shipped on top of it).
A stretch of stability also tends to surface what's still missing. One pattern that kept coming up (#28, #193, #855) was a different kind of widget than the AFM had been designed around.
Prior to v0.11, anywidget was a good fit for widgets that own a self-contained piece of the screen (a chart, a map, a control). Two limitations got in the way of anything else:
ipywidgets.HBox/ipywidgets.VBoxin Jupyter,mo.hstack/mo.vstackin marimo). Container widgets that ship as a single anywidget primitive were not expressible.panTo(lat, lng)orhighlight(rowId)on another widget on the page had to round-trip through a synced trait.v0.11 closes both gaps with three additions to the front-end contract.
For the full narrative, see the blog post: anywidgets All the Way Down.
For the formal spec, see the updated AFM specification.
What's new
signal(AbortSignal) oninitializeandrender(#974)Both
initializeandrendernow receive anAbortSignalvia thesignalprop. The host aborts it when the widget is destroyed (or during HMR). This is the preferred way to manage cleanup going forward, since it composes with web platform APIs that already accept anAbortSignal(addEventListener,fetch, child widgets):Returning a cleanup callback from
render(orinitialize) still works, so existing widgets need no changes. New code is encouraged to prefersignal.initializeMAY return anexportsobject (#974)initializeruns once per widget instance. In v0.11, it MAY return a plain object: the widget's exports. The host stores it and exposes it to other widgets that resolve this one as a reference (next section).The return type is distinguished by
typeof: functions are still treated as cleanup callbacks (existing behavior), objects are treated as exports, andvoidmeans neither.There is no schema and no validation. Widget authors define their own interfaces and consumers duck-type at the boundary.
host.getWidgetandhost.getModelfor widget composition (#974)rendernow receives ahostprop with two methods that resolve a child widget by reference:host.getWidget(ref)awaits the child'sinitializeand returns{ exports, render }.host.getModel(ref)returns the child's underlyingAnyModelfor direct event subscriptions orget/set/sendaccess without participating in rendering.Passing the parent's
signalthrough to the child'srenderties their lifecycles together: aborting the parent's view tears the child's view down too.On the Python side, widget references are serialized as
"anywidget:<model_id>"strings. A newWidgetTraittraitlet validates anywidget-compatible objects, and aWidgettype alias is provided for annotations:References work at any depth in synced state (top-level traits, values inside dicts, items inside lists).
Backward compatibility
Nothing is required to migrate. Existing widgets, including those returning cleanup callbacks from
renderorinitialize, continue to work unchanged. New widgets can opt intosignal,exports, andhostincrementally, hook by hook.If you maintain a host runtime, the host requirements for composition support are documented in the AFM spec. Hosts that do not (yet) implement composition should expose
hostonrenderand have its methods reject with a descriptive error rather than omitting the prop.Patch Changes
@anywidget/types@0.4.0v0.10.0Compare Source
Minor Changes
Drop Python 3.8 and 3.9 support, require Python >=3.10 (#949)
Python 3.8 and 3.9 have reached end-of-life. Bumping the minimum to 3.10 aligns anywidget with the broader ecosystem and allows us to upgrade dependencies (like
watchfiles) that have already dropped older Python support, which is needed for Python 3.14 compatibility.awslabs/serverless-application-model (aws-sam-translator)
v1.109.0: SAM v1.109.0 ReleaseCompare Source
What's Changed
New Contributors
Full Changelog: aws/serverless-application-model@v1.108.0...v1.109.0
v1.108.0: SAM v1.108.0 ReleaseCompare Source
What's Changed
New Contributors
Full Changelog: aws/serverless-application-model@v1.107.0...v1.108.0
v1.107.0: SAM v1.107.0 ReleaseCompare Source
What's Changed
Full Changelog: aws/serverless-application-model@v1.106.0...v1.107.0
python-babel/babel (babel)
v2.18.0Compare Source
Happy 2026! This release is, coincidentally, also being made from FOSDEM.
We will aspire for a slightly less glacial release cadence in this year;
there are interesting features in the pipeline.
Features
11841194121311961246Other improvements
12281230122712291174118911861202123312401197pyproject.tomlby @tomasr8 in :gh:1187unittesttest cases to bare functions by @akx in :gh:1241boto/boto3 (boto3)
v1.43.2Compare Source
======
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.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.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.iam: [botocore] Added guidance for CreateOpenIDConnectProvider to include multiple thumbprints when OIDC discovery and JWKS endpoints use different hosts or certificatesiot: [botocore] AWS IoT HTTP rule actions now support cross-topic batching, combining messages from different MQTT topics into single HTTP requests.logs: [botocore] Adds support for filtering log groups by tags in the ListLogGroups API via the new logGroupTags parameter.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.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.1Compare Source
======
bedrock-agentcore: [botocore] AgentCore Identity now supports on-behalf-of token exchange OAuth2. AgentCore Memory now supports metadata for LongTerm Memory Records.bedrock-agentcore-control: [botocore] AgentCore Identity now supports on-behalf-of token exchange OAuth2. AgentCore Memory now supports metadata for LongTerm Memory Records.datazone: [botocore] Adds support for asynchronous notebook runseks: [botocore] Vended logs update param for capability vended logs featurekafka: [botocore] Adds support for ZookeeperAccess field to control the Client-Zookeeper connectivity.observabilityadmin: [botocore] Observability Admin enablement launch for AWS Kafka, Bedrock Agent Core Workload Identity and OTel metric enablement.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.route53globalresolver: [botocore] Adds support for regions in the UpdateGlobalResolver input.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.sso-admin: [botocore] Add InstanceArn and IdentityStoreArn in the response of CreateApplication API and IdentityStoreArn in the response of DescribeApplication APIv1.43.0Compare Source
======
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.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 reportingbedrock-agentcore-control: [botocore] Adds configuration bundles for versioned, immutable agent configuration snapshots with branch-based lineagecloudfront: [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.deadline: [botocore] Adds support for rtx-pro-server-6000 GPU accelerator for service-managed fleets.ecr: [botocore] Removes support for registry policy V1gamelift: [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.mediapackagev2: [botocore] This feature adds configuration for specifying SCTE marker handlinConfiguration
📅 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 was generated by Mend Renovate. View the repository job log.