Skip to content

Release RC packages (rc) - #4683

Open
github-actions[bot] wants to merge 1 commit into
nextfrom
changeset-release/next
Open

Release RC packages (rc)#4683
github-actions[bot] wants to merge 1 commit into
nextfrom
changeset-release/next

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 4, 2026 •
edited
Loading

Copy link
Copy Markdown

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.

⚠️⚠️⚠️⚠️⚠️⚠️

next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@solidjs/babel-plugin@2.0.0-rc.22

Patch Changes

  • d70dda5: Carry authored istanbul/c8 ignore pragmas through the remaining Cannot use istanbul ignore comments for generated code #2138 cases: a pragma immediately before a component (including through a fragment) leads that component's children getter, pragmas inside fragments are preserved, and SSR prop-hoist copies them onto the shared descriptor's get().
  • bf71c28: DOM output no longer declares positional walks to nodes nothing reads. A text node ahead of an appended expression, like User : in <h1>User : {name()}</h1>, used to get var _el$3 = _el$2.firstChild even though the insert appends with a null marker. A minifier keeps that property read, since it could be a getter, so it shipped as _el$2.firstChild;. Both compilers now drop a firstChild/nextSibling walk when no later statement reads its node, including a walk that only fed another dropped walk.
  • 96ffcf7: Production builds compile a <Show> that needs no component to the ternary it renders: no keyed, no spread, only when and fallback, with JSX children or a one-parameter callback whose when is a plain read (each u() reads when again). Dev builds keep the component and its stale-read error. The lowerShow option overrides the default (!dev). The native compiler's SSR pass also no longer returns a TSRX module's static templates unescaped when one element in the module is marked as safe.
  • b2cb0c7: The server build escapes string literals in a ternary branch, after &&, and in every return of a function child, including a return inside if, switch, try or a loop. The server now renders them as text, as the client does, in children and in attribute values (Server build does not escape a string literal in a ternary branch or after && #4710). A function value in an attribute keeps its literals as written at every depth, because the server stringifies its source.
  • 701cbb3: SSR escapes the children of <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

  • d70dda5: Carry authored istanbul/c8 ignore pragmas through the remaining Cannot use istanbul ignore comments for generated code #2138 cases: a pragma immediately before a component (including through a fragment) leads that component's children getter, pragmas inside fragments are preserved, and SSR prop-hoist copies them onto the shared descriptor's get().
  • bf71c28: DOM output no longer declares positional walks to nodes nothing reads. A text node ahead of an appended expression, like User : in <h1>User : {name()}</h1>, used to get var _el$3 = _el$2.firstChild even though the insert appends with a null marker. A minifier keeps that property read, since it could be a getter, so it shipped as _el$2.firstChild;. Both compilers now drop a firstChild/nextSibling walk when no later statement reads its node, including a walk that only fed another dropped walk.
  • 96ffcf7: Production builds compile a <Show> that needs no component to the ternary it renders: no keyed, no spread, only when and fallback, with JSX children or a one-parameter callback whose when is a plain read (each u() reads when again). Dev builds keep the component and its stale-read error. The lowerShow option overrides the default (!dev). The native compiler's SSR pass also no longer returns a TSRX module's static templates unescaped when one element in the module is marked as safe.
  • c3de743: A module constant read by a component the refresh pass hoisted above it folds into the template as it does without the refresh pass, so the dev client and the server agree on the hole and hydration no longer crashes ([compiler rc.21] Dev hydration crash: transformRefresh hoists components above module consts, so the client keeps a hole dynamic that SSR inlined #4791).
  • b2cb0c7: The server build escapes string literals in a ternary branch, after &&, and in every return of a function child, including a return inside if, switch, try or a loop. The server now renders them as text, as the client does, in children and in attribute values (Server build does not escape a string literal in a ternary branch or after && #4710). A function value in an attribute keeps its literals as written at every depth, because the server stringifies its source.
  • 701cbb3: SSR escapes the children of <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

  • 7b405e9: Add setTrustedTypesPolicy(policy), so Solid renders on pages that enforce require-trusted-types-for 'script'. The app passes a Trusted Types policy it created, and the runtime assigns the TrustedHTML that policy returns, for compiled template markup, for the server HTML the frames client parses, and for the html tagged template's text decoding. On the server it is a no-op, so an isomorphic entry can call it. Nothing changes for apps that do not call it.
  • Updated dependencies [366c0eb]
  • Updated dependencies [90d1a51]
  • Updated dependencies [3ce08e9]
  • Updated dependencies [8506dbf]
  • Updated dependencies [54456c9]
  • Updated dependencies [c50abb6]
  • Updated dependencies [246a491]
  • Updated dependencies [32b4294]
  • Updated dependencies [218fe4a]
  • Updated dependencies [dfb1812]
  • Updated dependencies [b38d592]
  • Updated dependencies [9c917ea]
  • Updated dependencies [7230c08]
  • Updated dependencies [c8c5eb1]
  • Updated dependencies [7b405e9]
  • Updated dependencies [b3731b0]
    • @solidjs/web@2.0.0-rc.22

@solidjs/signals@2.0.0-rc.22

Patch Changes

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 dynamic mount 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 start arrived 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.

  • e76279f: Dev now warns OPTIMISTIC_WRITE_WHILE_LOADING when an optimistic setter runs while its source, which has answered before, is loading a new question. The setter composes on the previous answer, and the new answer replaces the guess ([2.0 / next] A guess written while its source loads a new question runs over the previous question's answer #4795).

  • 32b4294: Fail renderToStream when the default serializer reports a synchronous error before the first flush, matching asynchronous failures. No HTML is sent, onCompleteAll is skipped, and createSSRResponse returns 500 when consuming the stream. An error an <Errored> contained does not fail the render when it cannot be serialized: its record and the rejection of its source, deferStream or streamed, are sent as a plain Error with its message, the fallback stays, and the error hook hears the failure once. A rejection nothing contained still fails the render.

  • 9c917ea: A ref callback that reads a sync memo on a row mounted while an async memo is in flight no longer leaves that update held forever ([2.0 rc.14+] A ref that reads a memo on a row mounted during an async memo's flight leaves the update held forever (production builds only) #4767). Refs run in the attribute effect's commit half with no owner; a memo born into the hold has only a staged value, and an ownerless read of it threw NotReadyError (A19 exception 1), which errored the effect mid-hold so the transaction never landed. runRefCallback now marks the read, and serve returns the staged value only when the ref's creating pass was born into that memo's hold (F-7); production ref() always goes through runRefCallback so the mark is present outside dev too.

  • 7230c08: A ref callback (ref={el => …}) now runs the way a render effect's callback runs at creation ([2.0 rc.21 / next] A non-keyed <Show>/<Match> branch hidden by an optimistic write throws a stale read from its ref on restore and halts reactivity #4761). It is untracked and runs in the context of the pass that creates the element, so its reads see what that pass is building. Before, it ran with no owner, so its reads were outside reads that saw the screen before the pass committed. A non-keyed <Show>/<Match> branch that an optimistic write had hidden could not come back: its ref read the narrowed accessor, got the old falsy condition, and threw a stale read that halted the app.

    A ref still owns nothing. In dev, creating a memo, effect or root inside it throws PRIMITIVE_IN_EFFECT_CALLBACK, and onCleanup inside it throws CLEANUP_IN_FORBIDDEN_SCOPE. Set those up in the factory that returns the ref, which runs in the component body. Writes, refresh, action calls and onFlush stay allowed in a ref, as in an effect callback.

  • c8c5eb1: Server rendering only treats nodes the runtime made as finished markup. ssr(), ssrElement() and the frames sink now stamp their nodes with the Symbol.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 a t key (or t, h and p), 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 [5755ddd]

  • Updated dependencies [cf32a50]

  • Updated dependencies [ce7b4bb]

  • Updated dependencies [aaf528d]

  • Updated dependencies [d476295]

  • Updated dependencies [f6b6737]

  • Updated dependencies [2789ca9]

  • Updated dependencies [db3d13d]

  • Updated dependencies [bc423eb]

  • Updated dependencies [5208944]

  • Updated dependencies [6751472]

  • Updated dependencies [5ecd72f]

  • Updated dependencies [4de85c2]

  • Updated dependencies [6b7474b]

  • Updated dependencies [dc33de6]

  • Updated dependencies [f00ce6f]

  • Updated dependencies [da402ca]

  • Updated dependencies [79b6541]

  • Updated dependencies [45498e3]

  • Updated dependencies [e0f31bc]

  • Updated dependencies [1bdd973]

  • Updated dependencies [0895916]

  • Updated dependencies [edeb5db]

  • Updated dependencies [a01fd92]

  • Updated dependencies [d00f055]

  • Updated dependencies [38b6f85]

  • Updated dependencies [4fe7532]

  • Updated dependencies [ccb438d]

  • Updated dependencies [78eaf88]

  • Updated dependencies [cd4de28]

  • Updated dependencies [e76279f]

  • Updated dependencies [8b7254a]

  • Updated dependencies [46a72c0]

  • Updated dependencies [abbb806]

  • Updated dependencies [6681c1b]

  • Updated dependencies [a8b8b67]

  • Updated dependencies [9c917ea]

  • Updated dependencies [7230c08]

  • Updated dependencies [9d4f077]

  • Updated dependencies [fb672ca]

  • Updated dependencies [e76279f]

  • Updated dependencies [b050983]

  • Updated dependencies [9de15ba]

  • Updated dependencies [d06e7a7]

  • Updated dependencies [c981680]

  • Updated dependencies [b3e9fb8]

  • Updated dependencies [bcef104]

  • Updated dependencies [eef34fd]

  • Updated dependencies [ebd6283]

    • @solidjs/signals@2.0.0-rc.22

@solidjs/universal@2.0.0-rc.22

Patch Changes

  • 9c917ea: A ref callback that reads a sync memo on a row mounted while an async memo is in flight no longer leaves that update held forever ([2.0 rc.14+] A ref that reads a memo on a row mounted during an async memo's flight leaves the update held forever (production builds only) #4767). Refs run in the attribute effect's commit half with no owner; a memo born into the hold has only a staged value, and an ownerless read of it threw NotReadyError (A19 exception 1), which errored the effect mid-hold so the transaction never landed. runRefCallback now marks the read, and serve returns the staged value only when the ref's creating pass was born into that memo's hold (F-7); production ref() always goes through runRefCallback so the mark is present outside dev too.

  • 7230c08: A ref callback (ref={el => …}) now runs the way a render effect's callback runs at creation ([2.0 rc.21 / next] A non-keyed <Show>/<Match> branch hidden by an optimistic write throws a stale read from its ref on restore and halts reactivity #4761). It is untracked and runs in the context of the pass that creates the element, so its reads see what that pass is building. Before, it ran with no owner, so its reads were outside reads that saw the screen before the pass committed. A non-keyed <Show>/<Match> branch that an optimistic write had hidden could not come back: its ref read the narrowed accessor, got the old falsy condition, and threw a stale read that halted the app.

    A ref still owns nothing. In dev, creating a memo, effect or root inside it throws PRIMITIVE_IN_EFFECT_CALLBACK, and onCleanup inside it throws CLEANUP_IN_FORBIDDEN_SCOPE. Set those up in the factory that returns the ref, which runs in the component body. Writes, refresh, action calls and onFlush stay allowed in a ref, as in an effect callback.

  • Updated dependencies [cf839ea]

  • Updated dependencies [c50abb6]

  • Updated dependencies [e76279f]

  • Updated dependencies [32b4294]

  • Updated dependencies [9c917ea]

  • Updated dependencies [7230c08]

  • Updated dependencies [c8c5eb1]

    • solid-js@2.0.0-rc.22

@solidjs/web@2.0.0-rc.22

Patch Changes

  • 366c0eb: renderToStream().pipe() no longer throws buffer.flush is not a function when the render is abandoned from inside its first write ([2.0 rc.21 / next] renderToStream: a render abandoned inside pipe's first write throws "buffer.flush is not a function" #4745). With a shell of 16384 characters or more, a pre-flush redirect in createSSRResponse, a sink whose write throws or a signal aborted from inside that write left pipe flushing a buffer that had no flush, and the unhandled rejection ended the process under Node's default handling.

  • 90d1a51: A viewer that joins a running broadcast is 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).

  • 3ce08e9: A string class value no longer stores a property on the element when it is rendered on the client. className() cleared its applied-classes snapshot with node._$classes = undefined before every string write, which added an own property to each element the first time its class was set, even though only an object class value ever fills that snapshot. It now clears the snapshot only when one exists. Mounting 1,000 table rows with six string class bindings each allocates about 118 KB less (1,793 KB to 1,675 KB), and a uibench tree render is 5 to 10% faster. Behavior is unchanged. The hydrating path still seeds the snapshot as before.

  • 8506dbf: fix(web): a deferStream source that rejects on the server hydrates as a rejection, so reset() refetches it on the client (Hydration: a rejected deferStream source is adopted as a value, so reset() shows the Error and never refetches #4747)

  • 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 an attr op.

  • c50abb6: A dynamic mount 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 start arrived 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.

  • 246a491: insert no longer carries the portal host tagging in a bundle that renders no <Portal>: Portal installs it on first use. A hand-written insert(..., { host }) outside Portal now needs installHostTagging() first.

  • 32b4294: Fail renderToStream when the default serializer reports a synchronous error before the first flush, matching asynchronous failures. No HTML is sent, onCompleteAll is skipped, and createSSRResponse returns 500 when consuming the stream. An error an <Errored> contained does not fail the render when it cannot be serialized: its record and the rejection of its source, deferStream or streamed, are sent as a plain Error with its message, the fallback stays, and the error hook hears the failure once. A rejection nothing contained still fails the render.

  • 218fe4a: The DOM list reconciler no longer throws NotFoundError when user code moved a list node past the end of its list and the same update removes or replaces that node. The append step used the node after the list as its anchor even after the pass had taken it out of the parent; it now falls back to the marker, or the end of the parent.

  • dfb1812: The DOM list reconciler does less work for common small edits. A node moved from one end of a list to the other takes one DOM move, a list whose nodes did not change returns before reading the parent, and the window map is an index stamp on the new nodes instead of a Map. On the Octane board js-framework's reorder operations take about 20% less time and a text hole beside sibling nodes updates about 13% faster. Bundles with the web runtime are 33 bytes smaller minified.

  • b38d592: List reconciliation moves every connected node with Element.moveBefore() where the browser has it, not only the node holding focus, and no longer uses replaceChild() there. Moved rows stay connected, so focus and other node state survive any reorder, and a reorder places nodes instead of detaching and reattaching them: dbmon's 1,000-row sort drops from ~2.0 ms to ~0.75 ms, and shuffles and reverses get 3–7% faster. The per-pass document.activeElement read is gone. New nodes and browsers without moveBefore() keep insertBefore() as before.

  • 9c917ea: A ref callback that reads a sync memo on a row mounted while an async memo is in flight no longer leaves that update held forever ([2.0 rc.14+] A ref that reads a memo on a row mounted during an async memo's flight leaves the update held forever (production builds only) #4767). Refs run in the attribute effect's commit half with no owner; a memo born into the hold has only a staged value, and an ownerless read of it threw NotReadyError (A19 exception 1), which errored the effect mid-hold so the transaction never landed. runRefCallback now marks the read, and serve returns the staged value only when the ref's creating pass was born into that memo's hold (F-7); production ref() always goes through runRefCallback so the mark is present outside dev too.

  • 7230c08: A ref callback (ref={el => …}) now runs the way a render effect's callback runs at creation ([2.0 rc.21 / next] A non-keyed <Show>/<Match> branch hidden by an optimistic write throws a stale read from its ref on restore and halts reactivity #4761). It is untracked and runs in the context of the pass that creates the element, so its reads see what that pass is building. Before, it ran with no owner, so its reads were outside reads that saw the screen before the pass committed. A non-keyed <Show>/<Match> branch that an optimistic write had hidden could not come back: its ref read the narrowed accessor, got the old falsy condition, and threw a stale read that halted the app.

    A ref still owns nothing. In dev, creating a memo, effect or root inside it throws PRIMITIVE_IN_EFFECT_CALLBACK, and onCleanup inside it throws CLEANUP_IN_FORBIDDEN_SCOPE. Set those up in the factory that returns the ref, which runs in the component body. Writes, refresh, action calls and onFlush stay allowed in a ref, as in an effect callback.

  • c8c5eb1: Server rendering only treats nodes the runtime made as finished markup. ssr(), ssrElement() and the frames sink now stamp their nodes with the Symbol.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 a t key (or t, h and p), 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.

  • 7b405e9: Add setTrustedTypesPolicy(policy), so Solid renders on pages that enforce require-trusted-types-for 'script'. The app passes a Trusted Types policy it created, and the runtime assigns the TrustedHTML that policy returns, for compiled template markup, for the server HTML the frames client parses, and for the html tagged template's text decoding. On the server it is a no-op, so an isomorphic entry can call it. Nothing changes for apps that do not call it.

  • b3731b0: A text value that shares its parent with other children (<p>Count: {n()}</p>) no longer reads the text node's .data before each write. The node remembers the last value written and later updates compare against that, which takes a signal-driven text update from about 0.59 µs to about 0.35 µs. The first write to a node still compares with the DOM. One behavior difference: if something outside Solid rewrites such a text node and the value then re-evaluates to what Solid last wrote, the text is no longer written back.

  • Updated dependencies [cf839ea]

  • Updated dependencies [c50abb6]

  • Updated dependencies [e76279f]

  • Updated dependencies [32b4294]

  • Updated dependencies [9c917ea]

  • Updated dependencies [7230c08]

  • Updated dependencies [c8c5eb1]

    • solid-js@2.0.0-rc.22

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

@github-actions
github-actions Bot force-pushed the changeset-release/next branch 30 times, most recently from 1398c4d to cd0c63e Compare November 10, 2026 16:24
@github-actions
github-actions Bot force-pushed the changeset-release/next branch 29 times, most recently from 704c5e0 to dd078d3 Compare November 12, 2026 21:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants