chore(deps): update all non-major dependencies - #4521
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
commit: |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub. |
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 9, 2026 16:30
0a1139a to
674b0fa
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 10, 2026 10:04
674b0fa to
92b16aa
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 10, 2026 15:47
92b16aa to
299184c
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 10, 2026 19:44
299184c to
7928ad3
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 10, 2026 22:55
7928ad3 to
0927625
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 11, 2026 01:11
0927625 to
26862f4
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 11, 2026 22:17
26862f4 to
4e546df
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 12, 2026 08:50
4e546df to
f89e066
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 12, 2026 17:49
f89e066 to
86edf1d
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 13, 2026 04:17
86edf1d to
5c873c6
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 13, 2026 10:50
5c873c6 to
310035c
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 13, 2026 17:01
310035c to
c3c42dd
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 13, 2026 23:05
c3c42dd to
1fb077d
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 14, 2026 03:17
1fb077d to
cc4d984
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 14, 2026 16:59
cc4d984 to
c6e47ae
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:
^2.0.9→^2.0.10^5.20260716.1→^5.20260811.1^0.27.0→^0.31.2^1.62.7→^1.64.1^0.9.2→^0.9.4^26.1.1→^26.2.0^7.7.1→^7.8.0^10.1.0→^10.2.0^1.1.0→^1.1.1^4.14.0→^4.14.1^3.3.0→^3.3.1^2.0.1-rc.25→^2.0.1-rc.26^4.20260710.0→^4.20260730.0^0.3.22→^0.3.23^0.6.8→^0.6.9^0.59.0→^0.63.0^1.74.0→^1.78.011.13.1→11.21.0^1.2.0→^1.2.3^4.62.2→^4.62.4^0.9.1→^0.9.2^3.0.448→^3.0.451^0.7.6→^0.8.0^0.11.22→^0.12.5^6.3.0→^6.4.0^0.5.3→^0.6.0^8.1.4→^8.2.1^4.111.0→^4.120.1^1.1.2→^1.2.1bump,lockfileUpdate, orrollbackupdates, so these are raised without a Minimum Release Age check. You will need to manually validate the Minimum Release Age for these package(s).Release Notes
azure/static-web-apps-cli (@azure/static-web-apps-cli)
v2.0.10Compare Source
What's Changed
Bug Fixes
Full Changelog: Azure/static-web-apps-cli@v2.0.9...v2.0.10
cloudflare/workerd (@cloudflare/workers-types)
v5.20260811.1Compare Source
v5.20260810.1Compare Source
v5.20260809.1Compare Source
v5.20260808.1Compare Source
v5.20260807.2Compare Source
v5.20260804.1Compare Source
v5.20260801.1Compare Source
v5.20260731.1Compare Source
v5.20260730.1Compare Source
v5.20260729.1Compare Source
v5.20260728.1Compare Source
v5.20260727.1Compare Source
v5.20260726.1Compare Source
v5.20260724.1Compare Source
v5.20260723.1Compare Source
v5.20260722.1Compare Source
v5.20260721.1Compare Source
v5.20260719.1Compare Source
cloudflare/workers-sdk (@cloudflare/workers-utils)
v0.31.2Compare Source
Patch Changes
#15013
8cf78c8Thanks @dario-piotrowicz! - Update undici from 7.28.0 to 7.29.0#15011
6946da1Thanks @LeSingh1! - Validateobservability.logs.head_sampling_rateandobservability.traces.head_sampling_rateare between 0 and 1The 0–1 range check was only applied to the top level
observability.head_sampling_rate. The two nested fields were type-checked as numbers but never bounds-checked, so a value such as10(a common mix-up with a percentage) was accepted locally and sent to the API.{ "observability": { "logs": { "enabled": true, "head_sampling_rate": 10 } } }All three fields now report
must be a value between 0 and 1.consistently.v0.31.1Compare Source
Patch Changes
#15009
b5c083bThanks @LeSingh1! - Use the inherited Worker name when generating container names in named environmentsWhen
containersis declared inside a named environment and the container has no explicitname, the default container name was built from the environment's ownnamefield.nameis inheritable, so an environment that doesn't redeclare it left that valueundefined, producing the errorMust have either a top level "name" and "containers.class_name" field defined, or have field "containers.name" defined.even though a top levelnamewas set — and, if the error was ignored, a container namedundefined-<class_name>-<env>.{ "name": "my-worker", "env": { "staging": { "containers": [{ "class_name": "MyContainer", "image": "./Dockerfile" }] } } }wrangler deploy --env stagingon the configuration above now generatesmy-worker-mycontainer-staging, matching the documentedworker_name-class_name[-env_name]default. Anamedeclared on the environment still takes precedence over the top level one.v0.31.0Compare Source
Minor Changes
#14586
5a56ddaThanks @emily-shen! - MoveformatZodErrorfromminiflareto@cloudflare/workers-utilsThe
formatZodErrorand_forceColourhelpers are no longer exported fromminiflare; they are now exported from@cloudflare/workers-utils.v0.30.0Compare Source
Minor Changes
#14785
5e6556aThanks @dario-piotrowicz! - AddtoUrlPathandUrlPathexportstoUrlPath(filePath)converts a file-system path into a URL-safe path by replacing backslashes with forward slashes and rejecting Windows drive-letter prefixes (e.g.C:).UrlPathis the branded string type it returns, letting callers prove at the type level that a string has been normalized for use in URLs.v0.29.0Compare Source
Minor Changes
#14877
552bcfcThanks @jasoncabot! - Respect and surface theRetry-Afterheader on Cloudflare API responsesPreviously, if a Wrangler command (e.g.
wrangler versions upload,wrangler deploy) hit the Cloudflare API's rate limit, the resulting error gave no indication of how long to wait before trying again, and 429 responses weren't retried at all (only5xxerrors were, with a fixed linear backoff).Now:
429 Too Many Requestsresponses are automatically retried, alongside the existing5xxretry behaviour.Retry-Afterheader, Wrangler waits for that duration instead of the default backoff, and logs a message indicating how long it's waiting. To avoid blocking for an excessive amount of time, waits longer than 60 seconds fail fast instead — the surfacedRetry-Aftervalue lets the caller schedule its own retry.Retry-Afterduration, and thecommand-failedentry written to the Wrangler output file (WRANGLER_OUTPUT_FILE_PATH/WRANGLER_OUTPUT_FILE_DIRECTORY) gains aretry_after_msfield. This lets scripts and CI/CD pipelines calling Wrangler repeatedly (for example,wrangler versions uploadon every commit) read the wait duration directly instead of regex-parsing stderr.APIError.isRetryable()is unchanged (still5xxonly);retryOnAPIFailure()separately retries 429s.retryAfterMs, when present, is honoured for any retried error, not just 429s.retryAfterMsis also now populated onAPIErrors raised from direct R2 object requests, the Browser Rendering API, and errors surfaced from commands using the officialcloudflareSDK client.v0.28.0Compare Source
Minor Changes
#14595
2b390d7Thanks @colinhacks! - Recognise nub as a package managerwrangler now detects nub — from its
npm_config_user_agentand an installednubbinary — and autoconfig detects nub projects by theirnub.lock, alongside npm, pnpm, yarn, and bun.Patch Changes
#14746
a6c214fThanks @samarth70! - Return a clear error whenobservabilityis set tonullvalidateObservabilityguarded only againstundefined, so anullvalue (valid in JSON/JSONC config) passed thetypeof value === "object"check and then threwTypeError: Cannot read properties of null (reading 'enabled')while validating the config. It now rejectsnullwith the same"observability" should be an object but got null.diagnostic that the siblingcachevalidator already produces.scalar/scalar (@scalar/api-reference)
v1.64.1Patch Changes
#9828: Bump shared build and runtime dependencies to their latest compatible versions
(fuse.js, vite, vitest, tailwindcss, @vitejs/plugin-vue, @vue/test-utils,
posthog-js, yaml, and the CSS injection plugin). The fuse.js 7.5.0 upgrade
tightened generic inference, so the empty
new Fuse([])search instances nowpass an explicit
FuseDatatype argument.#9837: Keep the selected server when the configuration is updated. Pushing a config update to a mounted reference (for example a refreshed auth token via
updateConfiguration) rebases the document in the store, which previously reset the server selector back to the first server. The user's selected server is now preserved across configuration updates.#9783: fix: resolve axe-core ARIA violations in the API reference sidebar and client tabs
Sidebar items used
aria-selectedon links/buttons (invalid for those roles) and the search trigger usedrole="search"on a button. Selected items now usearia-current="page", the search control is a plain named button, and the sidebar no longer sets an invalidrole="navigation"on<aside>(it keeps the default complementary landmark).Client library and SDK installation "More" comboboxes sat inside
role="tablist", which failsaria-required-children. They now sit beside the tablist. MCP install controls without a target URL render as buttons instead of emptya[href=""]links.#9791: Stop recursive schema rendering when a discriminator variant
allOfs back to its base type. The selected child now inherits the parent's discriminator context so the mapping is not re-inferred on every nest.#9830: Stop listing enum values twice for an array parameter whose
itemsis a$refto an enum schema. The values are now listed only in the array items card, which
also shows the item schema's title and description.
#9839: Harden the API reference against untrusted OpenAPI documents:
info.license.url,info.termsOfService,info.contact.url,externalDocs.url,x-scalar-links) and the direct download link are nowchecked against an allow list of protocols, so a document can no longer render a
javascript:link that runs script when a reader clicks it. Unsafe values fall back to plain text.
deepMerge(used by the exportedcreateEmptySpecification) no longer writes through theprototype chain, so a document can no longer add properties to
Object.prototypevia__proto__,constructor, orprototype. Keys with those names are kept as plain data instead of beingdropped, so a schema is still free to describe a property named
constructor.customCsscan no longer close the injected<style>tag, which mattered during serverrendering where the value lands in the HTML stream verbatim.
rel="noopener noreferrer"to the remainingtarget="_blank"links.Adds
isSafeUrlandsanitizeUrlto@scalar/helpers/url/is-safe-url.#9829: Update Vue to 3.5.40. Vue 3.5.36 tightened
defineModeldefault validation, somodels with array or object defaults now use the factory form
(
defineModel<T[]>({ default: () => [] })) as Vue already requires for regularprops. Behaviour is unchanged.
#9790: fix: keep dots in webhook navigation deep links
Webhook event names that use dots (for example
account_holder.created) had thedot dropped when building the navigation id, joining adjacent words into
account-holdercreated. Dots are now kept, producingaccount-holder.created.Old deep links using the dropped-dot slug are redirected to the new slug, so
existing bookmarks keep resolving.
v1.64.0Minor Changes
#9683: Surface the required OAuth scopes for an operation as a dedicated "OAuth scopes" section below the description (above parameters), instead of only inside the "Auth Required" badge popover. Scopes are de-duplicated across security alternatives and shown in both the modern and classic layouts, as well as on AsyncAPI operations.
#9711: feat: add
pluginUrlsconfiguration option to load API Reference plugins from URLsEach entry must point to an ESM module that exports a plugin (the same shape as the
pluginsentries) as its default export. The standalone build (Scalar.createApiReference) imports the modules before the API reference mounts and registers their default exports alongside the plugins passed directly. Unlikeplugins, the new option is JSON-serializable, so integrations that pass their configuration as JSON (for example the Docker container or Scalar for Aspire) can load plugins without replacing the whole bundle.Patch Changes
#9732: Render every
oneOf/anyOfgroup of anallOfin place. Previously, when one object composed several mutually-exclusive choices as siblingoneOf/anyOfunderallOf, only the first group was shown and the rest were silently dropped. Each choice group now renders its own selector in the position it was declared, and the generated request example stays in sync per group.#9794: Keep sibling
propertieswhen flattening a single-memberallOf. Previously, a schema declaring its ownpropertiesnext to anallOfholding a single$reflost those sibling properties: the referenced schema'spropertiesoverwrote them instead of being combined, and the referenced schema'stitle/descriptionreplaced the parent's. Sibling and inherited properties now render together,requiredlists are unioned, and the parent schema's own annotations win over the base it extends.#9757: fix: read enum metadata from array items
When an enum is defined inside an array schema's
items, the enum values were resolved fromitemsbut theirx-enum-varnames,x-enumNames, andx-enumDescriptionswere still read from the outer schema, so the metadata was dropped. Both the values and their metadata are now read from the same schema.#9681: The "Auth Required" / "Auth Optional" badge on operations now opens on hover, not just on click
#9753: fix: badge base styles no longer rely on zero specificity
The badge base rule was written with
:where(.badge), which the scoped-style compiler collapsed to zero specificity, letting any late-loading reset clobber the badge font size, padding, and colors. The base styles now carry real specificity, and consumers that intentionally override them (the download-link json/yaml badges and the webhook badge) keep winning through tailwind-merge and higher-specificity variant rules.#9766: fix: give the collapsible section trigger an accessible name and a valid
aria-controlstargetThe trigger button rendered by
CompactSectioncarriedaria-controlsset to its ownid, so it declared that it controls itself, and it exposed no accessible name of its own. Screen reader users heard an unnamed button, and axe-core reportedbutton-nameandaria-allowed-attron every model section.The trigger now points
aria-controlsat the collapsible region, which carries its own id. While the section is collapsed the attribute is dropped entirely rather than left pointing at an element that is not rendered.The accessible name now comes from
aria-labelledbypointing at the heading the trigger already renders, so the name is always the visible text. Referencing the heading rather than copying it into anaria-labelmeans the name cannot drift out of sync with what is on screen, which is the WCAG 2.5.3 (Label in Name) failure a duplicated string would risk.#9754: fix: adapt the info links to the rendered width of the reference instead of the viewport
The introduction's info links (contact, license, terms of service, external docs, and
x-scalar-links), the section header grid, and the classic-layout selector cards switched their layout based on viewport media queries, while the rest of the reference adapts to the rendered width of the reference through thenarrow-references-containercontainer query. They now restyle based on the container as well, through a newnarrow:Tailwind variant.#9751: fix: keep even heading-to-description spacing on the operation title in narrow layouts
The narrow (single-column) operation layout bumped the operation title's bottom margin to 24px, so the gap between the heading and its description no longer matched the 12px used on wider screens. The override is removed so the title keeps the shared 12px spacing at every width.
#9676: Preload additional documents in a multi-document setup while the browser is idle, so switching between them is instant.
#9788: Add print styles so printing (or saving to PDF) no longer renders expanded content over the text that follows it. The reference lays itself out as a fixed-viewport application, and its sticky columns were pinned to a screen measurement that is meaningless on paper. Printing now flattens that shell into ordinary document flow: navigation and floating chrome are hidden, sticky positioning and viewport-derived height caps are dropped so long examples are no longer truncated, and small units such as properties and cards avoid breaking across pages.
#9691: Show the
formatof primitive array items (e.g. an array ofuuidstrings) in the schema property headingv1.63.0Minor Changes
SdkInstallationInstructionsandgetRenderableSdksfrom@scalar/api-reference/blocks, so consumers that compose their own reference layout can renderx-scalar-sdk-installationagainscalar/scalar (@scalar/openapi-types)
v0.9.4Patch Changes
.jsfile extensions to relative imports in the published2.0,3.0,3.1and3.2type declarations, so they resolve withmoduleResolution: nodenextandnode16sindresorhus/dot-prop (dot-prop)
v10.2.0Compare Source
d296823unjs/exsolve (exsolve)
v1.1.1Compare Source
compare changes
🩹 Fixes
importskeys with a trailer (#57)🏡 Chore
❤️ Contributors
privatenumber/get-tsconfig (get-tsconfig)
v4.14.1Compare Source
Bug Fixes
unjs/giget (giget)
v3.3.1Compare Source
compare changes
🏡 Chore
❤️ Contributors
h3js/h3 (h3)
v2.0.1-rc.26Compare Source
compare changes
🚀 Enhancements
mergeSlashesoption (9581407)htmltagged template (#1459)onDisposehook (#1488)🔥 Performance
resolveDotSegments(#1458)🩹 Fixes
nullorigin (#1464)-32600for valid-JSON non-object bodies (#1483)💅 Refactors
autocloseoption (#1495)📖 Documentation
event.url.pathnamedecoding (3f8b5bc)🌊 Types
RouteRulesinterface (#1474)StaticAssetMeta.path(0b34e24)🏡 Chore
H3Coretypes (978b17c)htmltagged template (#1459)autocloseoption (#1495)❤️ Contributors
cloudflare/workers-sdk (miniflare)
v4.20260730.0Compare Source
Minor Changes
#14685
01d7020Thanks @edmundhung! - Add JSON output to/cdn-cgi/handler/emailThe
/cdn-cgi/handler/emailendpoint now accepts?format=jsonto return the email handler result as JSON, including its outcome, rejection reason, forwarded messages, and replies. Requests withoutformat=jsonstill return the existing text outcome for backward compatibility.Patch Changes
#14929
48f0c6cThanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#14810
d7f38c3Thanks @allocsys! - Fix the local Images binding transform (env.IMAGES.input(...).transform(...)) ignoring thefit,gravity, andbackgroundoptions. Previously, local dev always letterboxed transformed images with black bars regardless of the options passed in. Local dev now respectsfit,gravity, andbackground, matching production Images binding behavior.#14850
5c25cfeThanks @exKAZUu! - Disable the keep-alive timeout on the loopback serverThe loopback server (which serves custom service bindings,
@cloudflare/vite-plugin's module transport, and other workerd → Node callbacks) used Node's defaultserver.keepAliveTimeoutof 5 seconds. workerd pools and reuses connections to the loopback server, so Node closing an idle pooled socket raced with workerd sending the next request on it, making that request fail withNetwork connection lost. The failure is probabilistic and load-dependent; under@cloudflare/vite-pluginwith a large SSR module graph and a cold optimizer cache (thousands offetchModulecalls with multi-second idle gaps between bursts), it broke most dev sessions. Disable the idle keep-alive timeout on the loopback server, mirroring the undici pools used for dispatch in the opposite direction.#14914
1f61001Thanks @nickpatt! - Capture Workflows invocations in local observabilityWhen local observability is enabled, the Workflows engine service is now attached to the trace collector (like every user worker), so workflow runs show up in the Local Explorer's Observability view attributed to the workflow. Previously the engine ran outside the per-user-worker tail wiring, so workflow invocations left no traces, spans, or logs in the local store.
v4.20260722.1Compare Source
Minor Changes
#14702
e426cb9Thanks @Sipixer! - Support passing V8 flags toworkerdvia theMINIFLARE_WORKERD_V8_FLAGSenvironment variableThe generated
workerdconfig already supportsv8Flags, but Miniflare never populated it, so the runtime always ran with V8's default heap limit (~1.4 GB). Large dev applications (e.g. big SSR module graphs under@cloudflare/vite-plugin, where each server-file edit grows the runner isolate's heap) can reach that limit, at which pointworkerdaborts withV8 fatal error; location = Reached heap limitand every subsequentdispatchFetch()fails withfetch faileduntil the dev server is manually restarted.Setting e.g.
MINIFLARE_WORKERD_V8_FLAGS="--max-old-space-size=4096"raises the limit and keeps long dev sessions alive. The variable follows the same space-separated format asMINIFLARE_WORKERD_AUTOGATES.#14280
465c0fbThanks @tahmid-23! - Add a local S3-compatible API for R2 buckets at/cdn-cgi/local/r2/s3/<bucket-id>, where<bucket-id>is the ID the bucket is configured with in ther2BucketsoptionBuckets configured with
s3Credentials: { accessKeyId, secretAccessKey }inr2Bucketsare served over an S3-compatible HTTP API, authenticated with AWS Signature Version 4 (bothAuthorizationheader and presigned URL query authentication). Supported operations: GetObject, HeadObject, PutObject, CopyObject, DeleteObject, DeleteObjects, ListObjects, ListObjectsV2, HeadBucket, ListBuckets, CreateMultipartUpload, UploadPart, UploadPartCopy, CompleteMultipartUpload, and AbortMultipartUpload. Status codes, error responses, and unsupported-header screening mirror R2's S3 endpoint, including its static responses for bucket-configuration reads and its named errors for unimplemented operations.#14712
6e0bf6eThanks @mack-erel! - Supportconnect()on remote VPC Network and VPC Service bindings in local developmentRemote VPC Network and VPC Service bindings previously only supported HTTP and JSRPC, so calling
binding.connect(address)against a private TCP service (for example a database) failed in local dev withIncoming CONNECT on a worker not supported. Raw TCP connections through remote VPC Network and VPC Service bindings now work in local development.This feature is experimental. Existing HTTP and JSRPC usage of remote VPC Network and VPC Service bindings is unaffected, and no new configuration is required.
Patch Changes
#14784
1035f74Thanks @ATKasem! - FixgetWithMetadatadropping metadata for falsy KV valuesKVNamespace.getWithMetadatareturnednullmetadata whenever the stored value was falsy — an empty string or"0"— because the metadata branch was guarded by a truthiness check on the value. The guard now checks fornullexplicitly, so metadata is preserved for empty-string and"0"values while genuinely missing keys still returnnull.#14864
3a22ae5Thanks @Hashim1999164! - Hide the workerd console window on Windows when the parent process has no console. Spawning workerd without `windowsHideConfiguration
📅 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.