Repository navigation
Release RC packages (rc) - #4683
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/next
branch
15 times, most recently
from
November 8, 2026 10:19
0022275 to
e51a8fb
Compare
github-actions
Bot
force-pushed
the
changeset-release/next
branch
from
November 8, 2026 10:21
e51a8fb to
a27e0ed
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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR will be updated.
nextis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonnext.Releases
@solidjs/babel-plugin@2.0.0-rc.22
Patch Changes
User :in<h1>User : {name()}</h1>, used to getvar _el$3 = _el$2.firstChildeven though the insert appends with anullmarker. A minifier keeps that property read, since it could be a getter, so it shipped as_el$2.firstChild;. Both compilers now drop afirstChild/nextSiblingwalk when no later statement reads its node, including a walk that only fed another dropped walk.<style>and<script>under<svg>and<math>. There they are ordinary elements whose text parses as markup, so only HTML-namespace<style>/<script>render raw text (<style>and<script>children inside MathML are not escaped in SSR (and static DOM templates), allowing markup injection #4704).@solidjs/compiler@2.0.0-rc.22
Patch Changes
User :in<h1>User : {name()}</h1>, used to getvar _el$3 = _el$2.firstChildeven though the insert appends with anullmarker. A minifier keeps that property read, since it could be a getter, so it shipped as_el$2.firstChild;. Both compilers now drop afirstChild/nextSiblingwalk when no later statement reads its node, including a walk that only fed another dropped walk.<style>and<script>under<svg>and<math>. There they are ordinary elements whose text parses as markup, so only HTML-namespace<style>/<script>render raw text (<style>and<script>children inside MathML are not escaped in SSR (and static DOM templates), allowing markup injection #4704).@solidjs/diagnostics@2.0.0-rc.22
Patch Changes
@solidjs/element@2.0.0-rc.22
Patch Changes
@solidjs/h@2.0.0-rc.22
Patch Changes
@solidjs/html@2.0.0-rc.22
Patch Changes
@solidjs/signals@2.0.0-rc.22
Patch Changes
f6b6737: Add
DEV.setSignalso development tooling can write signal values and store property slots (Add DEV.setSignal so devtools can write a signal or store node #4679).2789ca9: A display-ahead gate is the same mainline mount with any number of memos between the probe and the branch (S-58, D-25). A hand-written gate — one memo that probes and mounts, or a truthiness memo with a branch memo reading it — now keeps its fallback through the flight and attaches at the landing, as
<Show>and the compiled ternary do: a probe's held reader whose frame holds a born-held mount is no longer published with its hole empty when the probe re-derives to the same value at the seam, and a mount under an open action counts as still waiting. The plain read under an errored boundary inside an action (S-53′) attaches at the landing with it.5208944: Prevent an untracked staged-store read beside
latest()from throwing and halting reactivity when the store has no reactive node. A pass whose verdict posture is only inherited is now served the hold's own write from a node-less store key, as it is from a signal or a key with a node, so the landing frame no longer tears.6b7474b: An async memo that reads
isPending(x)no longer shows its verdict beside anisPending(x)binding that disagrees with it, and nothing derived from the write it reads ahead of shows before that write does ([2.0.0-rc.20] isPending disagrees with an async memo derived from it #4677).pending: trueshowed while the binding stayedfalse. The lane now reveals whole (F-6), and the landing's re-derivation follows next round.details: Item 1showed besideid: 0. Those runs now wait with the landing's held runs (F-1, F-7); what derives from a verdict reader still shows now (F-6, D-25).4fe7532: An optimistic guess corrected by an outside re-ask now stays the value for effects and untracked reads until its action's own refresh lands ([2.0 / next] A guess reverts at the action's end, before the refresh the action issued lands, once an outside re-ask has landed under it #4690). When a
refresh()from outside the action landed under a pending guess (createOptimistic, or acreateOptimisticStorekeyed, unkeyed or object-shaped), the action's hold stopped waiting on the guessed source's next flight. Where nothing rendered the source, the hold landed with the action's write, and effects and untracked reads showed the old truth until the action'srefresh()answered, while rendered readers (a render effect, a text node under<Loading>, an effect beside one) kept the guess. Rendered output never flickered; effect-only readers disagreed with it. A shown guess that was corrected now keeps its hold open while its own source is in flight, as an uncorrected guess does.46a72c0: A question is asked only of the truth (F-2's producer clause, F-6's limit), on the M1 lane value model. An async derivation that reads a held value plainly beside
latest()/isPending()is the hold's work: it asks once, of the truth, never of the value the screen keeps (S-51, [2.0.0-rc.20] isPending disagrees with an async memo derived from it #4677).isPendingstays true for a landed answer the lane still holds on a sibling's flight (S-54, 2.0.0-rc.21: isPending clears before a changed optimistic result is revealed #4685). A held recovery to the last good value is a change of answer andlatestshows it ahead, so an errored boundary recovers while the action is open (S-53, [2.0 / next] An action that un-poisons a throwing memo under an Errored showing its fallback (Show when=latest(m)) wedges the flush: Potential Infinite Loop Detected (last staged node: value) — async generator seed 3289 case 3963 #4403). A guess written to an optimistic memo before its first answer shows and the first answer judges it (S-56; the memo-formOPTIMISTIC_WRITE_BEFORE_LOADguard is gone, the store form keeps it).[isPending(x), x()]shows pending beside the kept value in every shape, a sync-ending action included (S-52, [2.0 rc.17 – next] refresh(memo) inside an action loops forever when a render effect reads isPending(memo) #4349). A plain write whose derivation became a guess's lane work holds on that flight and reveals with the lane (S-57). The branch a display-ahead<Show>opens is born held: the fallback stays through the flight and the branch attaches at the landing, for<Show>and the compiled ternary alike (S-46's plain row).latest()of a displayed optimistic guess keeps the guess over a correction until the commit, for a signal and a superseded keyed row ([2.0 / next] latest() over an optimistic guess answers the re-asked truth once a re-ask lands while the guess is pending #4689).Lane values now live on the node's two slots with the cover recorded explicitly (M1): the separate lane slot,
display()andlaneValueOfare gone.fb672ca:
IMMUTABLE_UPDATE_IN_STOREno longer reports wholesale replacements on a shallow store, or of amarkRaw/ unwrappable leaf (v2-rc.21: Shallow store produces diagnostic when replacing a value #4686). Those values are invalidated as a unit, so leaf draft assignment does not narrow who re-runs — the diagnostic's advice does not apply.solid-js@2.0.0-rc.22
Patch Changes
cf839ea: Context providers no longer create an owner of their own: the provided value now sits on the two memos that resolve the provider's children, so each provider allocates one node and one bound function fewer.
c50abb6: A
dynamicmount of a live server component that switches arguments and comes back to its first call (a windowed view scrolling back to the slice the page was served with) shows that call again. The equals gate compared the incoming binding with the one the memo holds, which is the first resolution's, so the way back read as "nothing changed" and the mount stayed on the other address.A live connection cancelled before its body's
startarrived now reads as a death, and the loop reconnects. A remount replaying a warm store gives up on a row-op record by cancelling the new connection so the resume re-sends the hole whole; with nothing open yet, the end read as a completion and the mount was left with no live connection.c8c5eb1: Server rendering only treats nodes the runtime made as finished markup.
ssr(),ssrElement()and the frames sink now stamp their nodes with theSymbol.for("solid.ssrNode")symbol (as$, a value no data can hold), and every insert position checks it instead of the object's shape. A plain object with atkey (ort,handp), such as one parsed from JSON, is data: it renders nothing and gets the dev warning UNRECOGNIZED_INSERT_VALUE, like any other plain object. The async-memo landing check (ASYNC_MEMO_ELEMENT) uses the same brand, so such data now serializes like other data instead of being refused. Server only; no client bytes.Updated dependencies [f6b6737]
Updated dependencies [2789ca9]
Updated dependencies [5208944]
Updated dependencies [6b7474b]
Updated dependencies [4fe7532]
Updated dependencies [46a72c0]
Updated dependencies [fb672ca]
@solidjs/universal@2.0.0-rc.22
Patch Changes
@solidjs/web@2.0.0-rc.22
Patch Changes
90d1a51: A viewer that joins a running
broadcastis sent each live range once, as it shows now. Its snapshot used to carry the frame as it first rendered and then every changed hole whole again, so a late joiner downloaded a big live table twice (about 600 ms to join a 2,000-row table, now about 120 ms).54456c9: A live server component's attribute whose value is still pending at the top of the render (no
<Loading>around it) no longer writes the live-hole comment markers inside the tag or the attribute value (<div<!--lh:1--> style="…"<!--lh:/1-->>), which broke the element. The element keeps its attribute address, and the binding registers once the tag's pending values resolve, so later values update the attribute as anattrop.c50abb6: A
dynamicmount of a live server component that switches arguments and comes back to its first call (a windowed view scrolling back to the slice the page was served with) shows that call again. The equals gate compared the incoming binding with the one the memo holds, which is the first resolution's, so the way back read as "nothing changed" and the mount stayed on the other address.A live connection cancelled before its body's
startarrived now reads as a death, and the loop reconnects. A remount replaying a warm store gives up on a row-op record by cancelling the new connection so the resume re-sends the hole whole; with nothing open yet, the end read as a completion and the mount was left with no live connection.c8c5eb1: Server rendering only treats nodes the runtime made as finished markup.
ssr(),ssrElement()and the frames sink now stamp their nodes with theSymbol.for("solid.ssrNode")symbol (as$, a value no data can hold), and every insert position checks it instead of the object's shape. A plain object with atkey (ort,handp), such as one parsed from JSON, is data: it renders nothing and gets the dev warning UNRECOGNIZED_INSERT_VALUE, like any other plain object. The async-memo landing check (ASYNC_MEMO_ELEMENT) uses the same brand, so such data now serializes like other data instead of being refused. Server only; no client bytes.Updated dependencies [cf839ea]
Updated dependencies [c50abb6]
Updated dependencies [c8c5eb1]
board-example@0.0.1-rc.7
Patch Changes
canvas-example@0.0.1-rc.3
Patch Changes
server-dbmon-example@0.0.1-rc.6
Patch Changes
todos-server-example@0.0.1-rc.10
Patch Changes
test-integration@2.0.0-rc.22
Patch Changes