Repository navigation
fix(deps): update all minor, patch, and digest updates - #27
Merged
Merged
Conversation
renovate
Bot
force-pushed
the
renovate/all-minor-patch-digest-updates
branch
from
October 17, 2026 02:44
787d98c to
a8c48c3
Compare
takumi3488
approved these changes
Oct 17, 2026
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.0-rc.14→2.0.0-rc.152.0.0-rc.14→2.0.0-rc.152.0.0-next.38→2.0.0-next.392.0.0-rc.14→2.0.0-rc.153.0.0-next.49→3.0.0-next.502.0.0-rc.14→2.0.0-rc.152.0.0-rc.14→2.0.0-rc.15Release Notes
solidjs/solid (@solidjs/babel-plugin)
v2.0.0-rc.15Compare Source
Patch Changes
617d195: Emit element claims after the element's initial attributes are applied (#3923), at parity across both compilers.A fully static
a[href]/form[action]is claimed at the end of its creation statements (after static writes and refs). An element with dynamic bindings captures its owner at creation (var _o$ = _$getOwner()) and is claimed as the last statement of its binding effect's callback —_$claimElement(_el$, _o$)— in both the single-binding and the multi-binding shapes, so the claim observes the applied values on the first run whether that run is synchronous or lands from a held flush. An element carrying a spread emits no compiled claim: thespreadruntime claims it after the first application.ca15970: Non-hydratable client builds now remove thevalueattribute when a checkbox or radio input binds a nullishvalueordefaultValue, matching the runtime fix from #4009, so a checked box submits"on"instead of"". Both compilers route these bindings throughsetPropertywhen the input's statictypeischeckboxorradio, or when itstypecannot be known at compile time (an expression,prop:type,attr:type). Text inputs, inputs without atype, and textareas still clear to""inline (#2957).43570f8: Reapply a select's bound value when its options arrive after the value was written.22f942d: SSR: a router can mark links in server HTML (#3878). Element claims never fire during SSR, so plain anchors arrived withoutaria-current="page"/data-active— late on hydrated pages, never on pages that do not hydrate. Both compilers now give every candidate<a href>in SSR output one hole after its attributes,ssrLinkClaim(attrs), where a render's link handler writes the anchor's link state and""otherwise. A static anchor's hole is one eager call over a hoisted attributes object (no allocation per render); a dynamic anchor's joins the element's attribute group and reuses the raw value itshrefhole evaluated. Anchors the compiler can rule out — a static non-emptytarget, adownload, arelnamingexternal, an author-writtenaria-current, an empty href or a non-HTTP scheme — get no hole at all. The hole creates no owner and takes no hydration id. A spread anchor's link attributes are collected byssrElementfrom its winning sources (an anchor's trailing link attributes stay a source instead of baked tail markup).New server API (
@experimental):setLinkClaim(handler)sets the handler of the render the caller belongs to — found through the owner chain likegetHydrationWriter(), so concurrent renders never share one — and returnsfalseoutside a render;undefinedclears it. The handler,(attrs) => string, receives the anchor's link-relevant attributes (href,target,rel,download,link,aria-current, raw values as written) and returns its attribute markup. An author-writtenaria-currentalways wins. Server components inline in the document render under the page's handler; a server component's own frame stream has none unless its render sets one.Trust marker: the first
setLinkClaimof a render writes thelinkshydration record once (_$HY.r.links = 1, with the shell's hydration script on the document face, a data record on a frame stream).hasServerLinkState()(client;falseon the server) reads it non-destructively, so a link consumer can tell "this page's anchors carry the server's link state" from "no handler ran" and trust the HTML at hydration instead of resolving every anchor's URL at claim. Without a handler the HTML and the hydration ids are byte-for-byte what they were.solidjs/solid-router (@solidjs/router)
v2.0.0-next.39Compare Source
Patch Changes
f3b5f56: Putstate,noscroll,replace, andpreloadback onJSX.AnchorHTMLAttributesby augmenting@solidjs/web/jsx-runtime.preloadalso accepts"viewport"and"eager".linkstays owned by core. Pairs with the core change that removes those four props from the anchor type.4a85130:intentPreloadpreloads a link once per visit whichever intent comes first: a focus or touch on a link that already preloaded no longer preloads it again, and cancels a pending hover preload. A click after a hover, or a click with no dwell, now sends one preload instead of two.ea24119: Follow client-side query redirects by status and origin. Keep local paths such as/nextand server-function redirects relative to the router base. Other same-origin URLs use the history parser without adding the base again; targets outside the base, or URLs the integration cannot represent, navigate the document. ALocationheader on a non-redirect response stays data on the client, and the server-function carrier takes precedence. Server rendering is unchanged.5729e79: Require solid-js / @solidjs/web 2.0.0-rc.15. Link and form claims follow rc.15's claim contract: an element's compiled mount claim fires once, after its initial attributes are applied, and later claims come from compiler-ownedhref/actionwrites or fromclaimElementTreesweeps (frame streams, morphs). The router's claim handlers are unchanged.af98854: Server-rendered anchors carry link state (#654). The router sets the render'slink handler (
setLinkClaimfrom@solidjs/web), so plain anchors arrive withdata-activeandaria-current="page"in the server HTML instead of gainingthem only after hydration, and pages that never hydrate mark the current page
too. When the client claims an anchor from that HTML, it treats a
server-written
aria-currentas its own and removes it on navigation. The peerfloor for
@solidjs/webandsolid-jsis raised to^2.0.0-rc.15.solidjs/solid-vite-plugin (@solidjs/vite-plugin)
v3.0.0-next.50Compare Source
Patch Changes
eb47535: Client start mode now strips the shell-end marker script along with the<HydrationScript />bootstrap.@solidjs/web2.0.0-rc.15 (solidjs/solid#4002) closes every shell that rendered<HydrationScript />with<script>_$HY.s[id]=1,…</script>, and a Document shared with SSR mode carries<HydrationScript />. Once the plugin stripped the bootstrap, that marker threw_$HY is not definedin client-mode shells, in dev and in the prerenderedindex.html. Shells from earlier@solidjs/webversions have no marker and are unchanged.6732a5f: The generated start-mode server handler no longer importsscriptNonce/styleNoncefrom@solidjs/web. It projects each destination of a{ script, style }nonce with a local helper instead. Those helpers are internal to@solidjs/web(solidjs/solid#4016), and its single-script surfaces now take the fullCSPNoncethemselves. The handler works with@solidjs/webversions both before and after that change.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.