Repository navigation
fix(deps): update all dependencies - #1678
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
|
|
❌ Deploy Preview for solid-docs failed. Why did it fail? →
|
renovate
Bot
force-pushed
the
renovate/all-dependencies
branch
from
October 30, 2026 00:07
e25c88d to
9ebba7e
Compare
renovate
Bot
force-pushed
the
renovate/all-dependencies
branch
from
October 30, 2026 05:44
9ebba7e to
5bf5676
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.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
0.13.12→0.13.14^0.6.13→^2.0.01.0.0→1.0.12.0.0→2.1.0^25.9.5→^26.0.08.65.0→8.72.18.65.0→8.72.1^17.4.2→^18.0.010.7.0→10.14.0^0.14.5→^0.18.017.7.0→17.13.011.20.0→12.16.13.9.6→3.9.101.22.12→1.22.131.9.14→1.9.188.65.0→8.72.18.2.4→8.3.5Release Notes
kobaltedev/kobalte (@kobalte/core)
v0.13.14Compare Source
Patch Changes
3d32663: ## v0.13.14 (September 7, 2026)Bug fixes
v0.13.13Patch Changes
cb89022: ## v0.13.13 (August 10, 2026)New features
Bug fixes
kobaltedev/solidbase (@kobalte/solidbase)
v2.0.0Compare Source
solidjs/solid-router (@solidjs/router)
v1.0.1Patch Changes
eaafba6: Stamp history depth from the current entry instead ofhistory.length, souseBeforeLeaveand scroll restoration keep working on Back once the browser's session history is full (#694)c3cbd67: Throw a descriptive error in development when an action is called directly instead of throughuseAction.473c270: Anchor click handling no longer intercepts links with a non-http(s) scheme (blob:,mailto:,tel:,data:, …). Previouslyblob:links could be wrongly routed because they inherit the page origin and bypassed the same-origin check.5a46ba1: Speed up<A>server rendering by roughly 5x<A>spent most of its server render time inmergePropsandsplitProps, which buildaccessor-backed prop objects that can never be observed during a one shot
renderToString. The defaultactiveClass/inactiveClassmerge is gone, thelocation.pathnamenormalization is shared instead of repeated per link,JSON.stringifyis skipped when there is no
state, and on the server a link that passes nothing beyondthe props
<A>consumes itself now skipssplitPropsand the JSX spread entirely.Rendered output is unchanged on the client, and unchanged on the server apart from the
linkmarker serializing aslinkrather thanlink="true"on that fast path. Clientbundles get slightly smaller, since the server branch is constant folded away.
65f9ee7: Fixes browser history navigation when Forward is pressed while a Back transition is waiting on route data.solidjs/solid-start (@solidjs/start)
v2.1.0Compare Source
Minor Changes
ad92979: Addssr: "data-only". The app renders on the client without hydration, as withssr: false, but the server runs the requested page's routepreloads and streams their query results with the HTML shell, so the client doesn't fetch that data again.Patch Changes
5de5afd: Bumpserovalandseroval-pluginsto 1.6.11.c30a825: Support a full URL in Vite'sbaseso assets can be served from a CDN, completing the base URL prefixing from 2.0.3. Entry, stylesheet, modulepreload and serialized manifest paths no longer collapsehttps://intohttps:/, and server functions post to the path the app is mounted at (server.baseURL, else Vite'sbasewhen it is a plain path, else/) instead of the asset base. There is no CDN in development: Vite serves the assets itself, including the public directory, under the URL's path, while the app stays at the root. Root-relative links to public files therefore differ between dev and a build; setting the CDNbasefor production builds only avoids that.2ff5882: Let aclientOnlyloader resolve to the component itself, so a named export works without wrapping it in{ default }:Destructuring the export inside the loader also lets the bundler leave the module's other exports out of the chunk.
45bacdb: Stop the dev toolbar's CSS from shipping in production builds. The error boundary statically imports the dev toolbar, whose module imports its stylesheet as a side effect. The toolbar is dead code in production, but the stylesheet survived because the package declared nosideEffects, so its styles were bundled into the client CSS. The package now marks only CSS files as having side effects, letting the bundler drop the toolbar and its styles from production output.9ce2a5d: Add anearlyHintsoption that sends the page's assets as103 Early Hints, so the browser can start downloading them while the server is still rendering. It covers the app's entry assets and the assets of the routes being rendered. On runtimes other than Node, the same hints are added asLinkheaders on the response. Off by default, and only applies to production builds.6c9b0c9: Fall back to client rendering when the browser's path or query changes before hydration starts, preventing hydration mismatches and stale server data after early navigation.a235891: Speed up the server function and lazy transforms."use server"are no longer parsed by the server function transform.for...oforfor...inloop variable, or a chain of unused declarations.017001e: Keep the result of a form submitted without JavaScript when its form data is too large for the flash cookie. Browsers silently drop cookies over 4096 bytes, so a large textarea used to makeuseSubmission()come back empty on the page the action redirected to. The form data is now left out of the cookie when it would not fit, the result and error still come through, and a warning is logged on the server.e0e6f6d: Reload the browser whenentry-serveror the middleware changes in dev. Both are server-only, so Vite had nothing to send the browser and the page kept showing the previously rendered output until it was refreshed by hand.6a9fb75: Reload the page once when a route's code fails to load during client-side navigation, such as when a deploy replaced it while the page was open. Before, the navigation ended on an error page until the user refreshed by hand. The page now reloads at the destination and loads the new version. A route that still fails right after the reload shows the error instead of reloading again. This only applies to production builds, and can be turned off withreloadOnRouteChunkError: false.207cfd2: Makesolid-jsa peer dependency instead of a regular one. When an app'ssolid-jsversion was outside the range SolidStart asked for, package managers installed a second copy just for SolidStart. The two copies did not share reactive context, so client-side navigation broke withTypeError: Cannot read properties of null (reading 'push'). SolidStart now uses the app'ssolid-js, and a version outside the supported range shows up as a peer dependency warning at install time.eb50f39: Serve pages in SPA mode (ssr: false) when a route file exports both a page and an API handler, such as a[...404].tsxwith aGET. The server treated those routes as API-only, so aGETthat returned nothing gave a 404 for every URL the route matched.ad92979: ExportgetServerFunctionMeta,decorateHandleranddecorateMiddlewarefrom@solidjs/start/serverin SPA mode (ssr: false), so apps using them build.v2.0.6Compare Source
Patch Changes
a4ed2a4: Stopclient-onlyfrom failing the build for lazily imported client components.A module that imported
client-onlyand was loaded throughclientOnly(() => import(...))failed the server build, even though it only ever runs in the browser. The server build resolves every dynamic import to emit its chunk, so it resolved theclient-onlymodule and rejected it, though that module never runs on the server.client-onlyno longer fails the build.server-onlyis unchanged and still fails a client build.048f5a9: Stop a no-JS server function POST from returning a 500 when the body is not a form.A POST to a server function without the client runtime, carrying an empty body or a non-form content type, left a value that is not a
FormDataas the last argument. Building the flash cookie called.entries()on it and threw, and the error handler rethrew the same way, so the request failed with a 500. The response is now the normal redirect, and the flash cookie is best effort so it can no longer take down the error path.59e7dc7: Make reading server function streams safer and faster.d34acf5: Require seroval and seroval-plugins 1.6.8 or newer.d34acf5: SendCache-Control: no-storeon server function responses by default.Server function responses, including calls made with GET, carried no
Cache-Control, so a shared cache configured to store them could serve one caller's result to another. Every response from the server function handler now defaults tono-store: results, errors, redirects, no-JS redirects, rawResponsepassthroughs, and the handler's own refusals. ACache-Controlthe function sets itself, on a returnedResponseor on the event's response headers, is kept as is, and a304is never given one.d34acf5: Reject cross-site server function requests.A
"use server"function could be invoked from another site with the visitor's cookies, over a GET or a form POST, because the request's origin was not checked. Requests to server functions are now allowed only from the same origin or same site. The check trusts theSec-Fetch-Siteheader and falls back to comparingOriginagainst the request host, so a page on another site receives a403instead of running the function. Same-origin calls, user-initiated navigations, and no-JS form submissions are unaffected. A separate origin that needs to call your backend should use an API route with explicit CORS.9d3cbec: Report server functions that cannot work instead of compiling them into broken output."use server"function that reads a variable from an enclosing function now fails the build. The function is moved to the top level of its module, so the variable is not in scope when it runs.thisandargumentsin an arrow function,super, and private class members."use server"directive in an object or class method now fails the build. It was ignored before, which shipped the method body and the modules it imports to the browser."use server"string that is not the first statement of a module or a function body now logs a warning. It has no effect there."use server"module cannot serve now logs a warning that names it. These exports are still left out of the client build."use server"module can now export an anonymous default function. Bothexport default async () => {}andexport default async function () {}work.Page.load, instead of the order the functions appear in. An id no longer changes when another server function is added to the same file, and two functions that share a name are told apart by the names around them. Production ids stay opaque..mtsand.ctsfiles.d34acf5: Treat a server function request withOrigin: nulland noSec-Fetch-Siteas cross-site.Browsers send
Origin: nullfrom opaque origins, such as sandboxed iframes and some cross-origin redirect chains. WhenSec-Fetch-Sitewas absent, the handler skipped theOrigincomparison for that value and allowed the request. It is now refused with a403. Requests that carry neither header, such as those from non-browser clients, are still allowed.d34acf5: Settle server function values that are still waiting on the stream when its body ends.A seroval body can reference a promise or stream that a later frame settles. If the body ended before that frame arrived, the value stayed pending forever, so a server function awaiting such an argument never answered. A malformed later frame also surfaced as an unhandled rejection. When the body ends or fails, every promise still waiting on it now rejects (with the failure, or with "Server function stream ended unexpectedly.") and every open stream errors. Decoded promises that nobody awaits no longer report unhandled rejections; code that awaits them still sees the rejection.
v2.0.5Compare Source
Patch Changes
eca4cc4: Only strip a wholeindexsegment when mapping route files to paths. Route files whose names merely end in "index", such asroutes/reindex.tsx, were previously served at/reinstead of/reindex.v2.0.4Compare Source
Patch Changes
ac3f321: Parse stack traces in the dev toolbar's error overlay witherror-stack-parser-es/liteinstead oferror-stack-parser. The lite entry point is a much smaller, ESM-only parser that returns plain frame objects rather than class instances, and it no longer pulls in thestackframepackage. Errors that carry no stack are now handled as an empty frame list instead of throwing.ac3f321: Redesign the dev toolbar. The toolbar and its panels share a common set of design tokens, giving them a consistent dark palette, translucent surfaces, and elevation. The server function inspector is now a master-detail split with a persistent call list beside the request/response pane, and the error overlay places the stack frame list beside a code preview that fills the panel. Headers, form data, and URL search params render as aligned key-value tables, the hex viewer gains an offset gutter with the ASCII column aligned per row, and blobs are shown as file cards with their type and size. The seroval body inspector is now an expandable tree with collapsed previews, syntax-colored values, cycle detection, and live promise and stream state, replacing the previous column-based drill-down.Along with the redesign, the toolbar only starts a drag from the toolbar itself rather than from its panels, unhandled promise rejections are captured by the error overlay, the code preview shows more surrounding lines, and a stack frame whose source cannot be loaded now stays listed and reports that its source is unavailable instead of silently rendering nothing.
ac3f321: Use@jridgewell/trace-mappinginstead ofsource-map-jsto resolve original sources in the dev toolbar's error overlay. It decodes mappings lazily, so only the positions actually inspected are resolved, it is significantly smaller in the browser bundle, and it understands indexed source maps.f619c7f: Pre-bundle the dev toolbar's CommonJS dependencies so it no longer throws on every dev page loadd43ad1b: Update Solid to 1.9.15 to include the latest lazy loading and hydration fixesv2.0.3Compare Source
Patch Changes
91fc972: Prefix production entry scripts, stylesheets, modulepreloads, and serialized manifest paths with Vite's configured base URL.v2.0.2Compare Source
Patch Changes
e21fadf: fix potentially incomplete first chunk for chunk readersd78288f: Declare an explicitContent-Type: text/plain; charset=utf-8on seroval-stream server function responses (success and error paths) so intermediaries cannot content-sniff a type onto themv2.0.1Compare Source
Patch Changes
fd5e2ae: Delegatevite previewto Nitro when its preview plugin is active, including for static builds that intentionally have no server entry.typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v8.72.1Compare Source
🩹 Fixes
❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.72.0Compare Source
🚀 Features
allowMixedPromiseArraysoption (#12992)🩹 Fixes
❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.71.2Compare Source
🩹 Fixes
❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.71.1Compare Source
🩹 Fixes
❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.71.0Compare Source
🚀 Features
🩹 Fixes
this: voidon class properties (7fce9127d)❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.70.1Compare Source
🩹 Fixes
await(#12716)❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.70.0Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.69.0Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.68.0Compare Source
🚀 Features
🩹 Fixes
ignoreVoid: falseresults in false negative in ArrowFunctionExpression (#12646)❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.67.0Compare Source
This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.66.0Compare Source
🩹 Fixes
❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v8.72.1Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.72.0Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.71.2Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.71.1Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.71.0Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.70.1Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.70.0Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.69.0Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.68.0Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.67.0Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.66.0Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
motdotla/do
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 was generated by Mend Renovate. View the repository job log.