chore(deps): update all non-major dependencies#61
Merged
Conversation
a147ad2 to
4600d87
Compare
4600d87 to
a737d7e
Compare
a737d7e to
b1740e0
Compare
b1740e0 to
62eff77
Compare
62eff77 to
d6895e9
Compare
d6895e9 to
bec5c88
Compare
bec5c88 to
fc5e938
Compare
fc5e938 to
8d18c96
Compare
8d18c96 to
562c8e5
Compare
562c8e5 to
5fab7b0
Compare
5fab7b0 to
a597d89
Compare
a597d89 to
28b90f5
Compare
28b90f5 to
ff660a1
Compare
ff660a1 to
d3bfad2
Compare
d3bfad2 to
0e77c8e
Compare
0e77c8e to
80c99b9
Compare
80c99b9 to
16d5374
Compare
16d5374 to
b547f4a
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:
^3.0.121→^3.0.126^3.0.193→^3.0.198^0.3.1→^0.4.0^0.4.6→^0.5.1^1.2.84→^1.2.86^4.8.1→^4.8.2^4.1.0→^4.2.0^3.24.0→^3.26.0^3.24.0→^3.26.0^3.24.0→^3.26.0^3.24.0→^3.26.0^3.24.0→^3.26.0^3.24.0→^3.26.0^3.24.0→^3.26.0^3.24.0→^3.26.0^25.9.1→^25.9.2^6.0.193→^6.0.19811.5.0→11.5.2^4.1.0→^4.2.0^3.3.3→^3.3.44.2.5→4.3.1Release Notes
vercel/ai (@ai-sdk/gateway)
v3.0.126Compare Source
Patch Changes
ff16d3b: feat(gateway): add GatewayFailedDependencyError (424)v3.0.125Compare Source
Patch Changes
fef3b24: Backport: chore(provider/gateway): update gateway model settings filesv3.0.124Compare Source
Patch Changes
286b7a2: Backport: chore(provider/gateway): update gateway model settings filesv3.0.123Compare Source
Patch Changes
537a022: Backport: chore(provider/gateway): update gateway model settings filesv3.0.122Compare Source
Patch Changes
9766034: Backport: chore(provider/gateway): update gateway model settings filescomarkdown/comark (@comark/nuxt)
v0.4.0: @comark/nuxt v0.4.0Compare Source
0.4.0 (2026-06-04)
electric-sql/pglite (@electric-sql/pglite)
v0.5.1Compare Source
Patch Changes
930e2d0: fix PGlite version; redeploy external extensionsv0.5.0Minor Changes
93d50aa: Upgrade to Postgres 18.3; move other extensions to their own npm packages;nuxt/ui (@nuxt/ui)
v4.8.2Compare Source
Bug Fixes
nameattribute (#6539) (f8186e2)localeprop (#6546) (ed2f955)shikijs/shiki (@shikijs/langs)
v4.2.0Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
ueberdosis/tiptap (@tiptap/core)
v3.26.0Patch Changes
v3.25.0Compare Source
Patch Changes
ec291dd: Fix: dragging an inline/resizable image within the editor no longer creates a duplicateWhen the
Imageextension was configured withinline: trueorresizeenabled, dragging an image within the editor could insert a duplicate at the drop position instead of moving it. This happened because the browser's native image drag behavior could populatedataTransfer.files, causing the FileHandler extension to intercept the drop before ProseMirror's internal move logic could run.454e9b8: Addclearablemark option (defaulttrue).unsetAllMarksnow skips marks withclearable: false, so semantic marks like comments are not removed by "clear formatting".9cf8db0: AddattrsEqualandmarksEqualutility functions to@tiptap/core.attrsEqualcompares two attribute objects for equality regardless of key ordering.marksEqualcompares two arrays of mark objects by type and attributes usingattrsEqual.3d4f94c: Fix plain-text copy of table cell selections including content from unselected cells in between. Each selected range is now serialized independently and joined in document order, so dragging upward (reverse selection) also produces output in document order.Updated dependencies [
c1a2ce8]ueberdosis/tiptap (@tiptap/extension-details)
v3.26.0Patch Changes
v3.25.0Compare Source
Patch Changes
ec291dd]454e9b8]9cf8db0]c1a2ce8]3d4f94c]ueberdosis/tiptap (@tiptap/extension-emoji)
v3.26.0Patch Changes
v3.25.0Compare Source
Patch Changes
ec291dd]454e9b8]9cf8db0]c1a2ce8]3d4f94c]ueberdosis/tiptap (@tiptap/extension-list)
v3.26.0Patch Changes
v3.25.0Compare Source
Minor Changes
45237e7:ListKeymap's Backspace handler now lifts the current list item before merging. At the start of a non-first list item, the item is lifted out of its wrapping list (splitting the list around it) instead of immediately joining its content into the previous item. A second Backspace then hits the existing "paragraph after a list" branch and merges the lifted textblock's content into the previous list's last item. Mirrors the two-step behavior introduced for blockquote in #7891.Patch Changes
8dc5694: Fix delete at the end of a list item with a branching nested sublist. Nested items are hoisted to the parent list instead of being node-selected and deleted on the next keypress.ec291dd]454e9b8]9cf8db0]c1a2ce8]3d4f94c]ueberdosis/tiptap (@tiptap/extension-mention)
v3.26.0Patch Changes
v3.25.0Compare Source
Patch Changes
ec291dd]454e9b8]9cf8db0]c1a2ce8]3d4f94c]ueberdosis/tiptap (@tiptap/extension-table)
v3.26.0Patch Changes
v3.25.0Compare Source
Patch Changes
86e29ec: FixHTMLAttributesnot being applied to the<table>element whenresizableis disabled (the default). TheTableViewnode view (introduced in 3.23) bypassedrenderHTMLand never applied user-configured attributes likeclassordata-*to the rendered table element.ec291dd]454e9b8]9cf8db0]c1a2ce8]3d4f94c]ueberdosis/tiptap (@tiptap/pm)
v3.26.0v3.25.0Compare Source
Patch Changes
c1a2ce8: Bumpprosemirror-tablesto^1.8.0sofindTableis available from@tiptap/pm, and align the related ProseMirror dependencies with the versions required byprosemirror-tables.ueberdosis/tiptap (@tiptap/vue-3)
v3.26.0Patch Changes
v3.25.0Compare Source
Patch Changes
26e6f0f: FixVueNodeViewRendererthrashing the DOM whencontentDOMis null for non-leaf nodes. The renderer now always creates a contentDOM element for non-leaf nodes (matching React's behavior), so ProseMirror has a valid element to render children into even when the NodeView component does not includeNodeViewContentor renders it conditionally.ec291dd]454e9b8]9cf8db0]c1a2ce8]3d4f94c]pnpm/pnpm (pnpm)
v11.5.2Compare Source
Patch Changes
Peer dependency resolution now reuses the peer contexts already recorded in the lockfile when those providers are still present in the dependency graph and still satisfy the peer ranges. This avoids unnecessary peer-context rewrites during lockfile regeneration. Current manifest choices remain authoritative: a newly added, explicitly updated, or aliased direct provider, a changed nested provider, or a locked version that no longer satisfies the range still takes precedence.
The lockfile verifier now checks that a registry entry pinning an explicit
tarballURL points at the artifact the registry's own metadata lists for thatname@version. Previously a tampered lockfile could pair a trustedname@versionwith an attacker-chosen tarball URL (and a matching integrity for those bytes), so the install fetched the attacker's bytes. A mismatch — or any entry that can't be confirmed against the registry — is rejected withERR_PNPM_TARBALL_URL_MISMATCH. Non-registry resolutions (file:, git-hosted, etc.) and registry entries without an explicit tarball URL (the URL is reconstructed from name+version+registry, so it is inherently bound) are unaffected; non-standard registry tarball URLs (npm Enterprise, GitHub Packages) still pass because they match the metadata.Fix
pnpm update --recursive --lockfile-only <pkg>@​<version>crashing withInvalid Versionwhen the catalog entry for<pkg>is a version range (e.g.^21.2.10) andcatalogModeisstrictorprefer. The catalog–version comparison now skips the equality check when either side is a range rather than passing a range tosemver.eq(), so range specifiers fall through to the existing mismatch handling instead of throwing #11570.Avoided a Node.js crash when pnpm exits after network requests on Windows.
Fixed packages being materialized into the virtual store without their root-level files (
package.json,LICENSE, README, root entrypoints) when multiplepnpm installprocesses ran against the same store/workspace concurrently. The fast import path used to destructively empty the shared target directory, so a concurrent importer could wipe files another importer had already written; if the surviving files included thepackage.jsoncompletion marker, every later install treated the broken directory as complete and never repaired it. The fast path now imports directly only when it can create the target directory exclusively, and otherwise builds the package in a private temp directory and atomically renames it into place #12197.Fix dependency build scripts not running under the global virtual store (
enableGlobalVirtualStore).In a workspace install, dependency build scripts are deferred to a single
rebuildpass (buildProjects). That pass resolved each package's location from the classicnode_modules/.pnpm/<depPathToFilename>layout, which does not exist under the global virtual store — so native dependencies (e.g. packages usingnode-gyp/prebuild-install) were never built and failed to load at runtime (Cannot find module .../build/Release/*.node).buildProjectsnow resolves the global-virtual-store projection directory (<storeDir>/links/<hash>, computed with the same graph hash the installer uses) whenenableGlobalVirtualStoreis set, and serializes concurrent builds of the same shared projection so parallel workspace projects don't race on the same directory.Don't promote a
runtime:dependency (such as the Node.js version fromdevEngines.runtimeorpnpm runtime set) into a catalog whencatalogModeisstrictorprefer. Aruntime:dependency round-trips todevEngines.runtime, which only recognizes theruntime:protocol; cataloging it rewrote the manifest entry tocatalog:, which broke that round-trip, stranded it indevDependencies, and leftdevEngines.runtimeuntouched.Skip lockfile
minimumReleaseAge/trustPolicyverification for non-registry tarball protocols (for examplefile:), so local tarball dependencies are not incorrectly checked against npm registry metadata.v11.5.1Compare Source
Patch Changes
pnpm auditperformance by pruning non-vulnerable lockfile subtrees and stopping path enumeration once vulnerable findings reach the path cap.npm_config_user_agentfor root lifecycle scripts during headless installs.integrityfield of a remote (non-registry) tarball dependency when its lockfile entry is rebuilt. Re-resolving such a dependency without re-fetching it (for example viapnpm update, or when another dependency changes) produced a resolution with no integrity — URL/tarball resolvers only learn the integrity after the tarball is downloaded — so the previously recorded integrity was dropped, making later installs fail withERR_PNPM_MISSING_TARBALL_INTEGRITY#12067.repositoryfield into the{ type, url }object form when creating the publish manifest, matching npm's behavior. Some registries (e.g. Gitea/Codeberg) reject a stringrepositorywith a 500 Internal Server Error duringpnpm publish#12099.@typescript-eslint/eslint-pluginpeer-depends on both@typescript-eslint/parserandtypescript, and@typescript-eslint/parserpeer-depends ontypescript), pnpm no longer reuses a hoisted instance of the shared peer that was resolved against a different version #12079.vuejs/language-tools (vue-tsc)
v3.3.4Compare Source
language-core
checkRequiredFallthroughAttributesis enabled (#6088) - Thanks to @KazariEX!htmlAttributesoption (#6089) - Thanks to @KazariEX!language-service
typescript-plugin
classandstyleas a boolean property (#6081) - Thanks to @KazariEX!vercel/workflow (workflow)
v4.3.1Compare Source
@workflow/world-vercel@4.3.2
5655fcb@VaguelySerious - Retry transient response-body read/decode failures (truncated or terminated streams, gateway non-CBOR bodies) on idempotent requests inside the HTTP client, so a sporadicevents.listparse failure no longer surfaces as a fatal error.v4.3.0Compare Source
@workflow/core@4.3.0
9092640@TooTallNate - AWritableStreamfrom a workflow'sgetWritable()can now be passed as an argument to a child workflow viastart(); the child's writes land on the parent run's stream directly for the full lifetime of the child run.5a0ce9a@pranaygp - Fix forwarded writable stream encryption when child workflows execute on a newer deployment than their parent.1e32d05@pranaygp - Prevent replayed workflows from advancing their deterministic clock when a future event is inspected before its matching operation is invoked.5fd7d9c@pranaygp - Retry transient workflow replay divergence before classifying repeated divergence as a corrupted event log.@workflow/world@4.1.4
5a0ce9a@pranaygp - Fix forwarded writable stream encryption when child workflows execute on a newer deployment than their parent.5fd7d9c@pranaygp - Retry transient workflow replay divergence before classifying repeated divergence as a corrupted event log.@workflow/errors@4.1.3
5fd7d9c@pranaygp - Retry transient workflow replay divergence before classifying repeated divergence as a corrupted event log.v4.2.6Compare Source
@workflow/core@4.2.6
e256858@pranaygp - Harden runtime event pagination against rejected, repeated, or overlapping cursor responses.38c67a7@TooTallNate - FixCorruptedEventLogErroron replay when a workflow races a hook read against asleep()(e.g.Promise.race([hook, sleep])). Branch-deciding deliveries (buffered hook payloads and wait completions) are now handed to the workflow in strict event-log order — anchored on event position rather than on microtask-resolution timing — so the committed branch wins the race deterministically, independent of decryption/hydration time orPromise.raceargument order.ebfeede@VaguelySerious - Harden workflow error stack remapping for large inline sourcemaps.3113738@pranaygp - Prevent failed stream writes from surfacing as unhandled rejections and include request correlation details in stream errors.@workflow/world@4.1.3
8ab6c4f@adamiBs - Makerun.inputandstep.input.optional()on the World snapshot schemas so consumers no longer fail validation when the service externalizes payloads asRemoteRefblobs.@workflow/world-local@4.1.3
2aecfdb@pranaygp - Reduce local stream metadata and pagination I/O by reading only EOF marker bytes and scanning chunk files once.@workflow/world-vercel@4.3.0
17cf939@TooTallNate - Add@workflow/world-vercel/run-idsub-export withencode/decodehelpers that produce ULID-shaped workflow run IDs carrying a tag bit, a 5-bit version, and a 6-bit Vercel region ID.3113738@pranaygp - Prevent failed stream writes from surfacing as unhandled rejections and include request correlation details in stream errors.@workflow/web@4.1.7
e313c66@karthikscale3 - Allow lookup of exact step ID (step_), wait ID (wait_), hook ID (hook_), or event ID (evnt_) in the event list UI.@workflow/web-shared@4.1.7
e313c66@karthikscale3 - Allow lookup of exact step ID (step_), wait ID (wait_), hook ID (hook_), or event ID (evnt_) in the event list UI.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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.