Skip to content

Release RC packages (rc) - #3724

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

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

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 30, 2026 •

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.14

Patch Changes

  • 3c1f809: Preserve /* istanbul ignore … */ and /* c8 ignore … */ block comments written as JSX children on the generated component children getter. Line comments are not carried.

@solidjs/compiler@2.0.0-rc.14

Patch Changes

  • 3c1f809: Preserve /* istanbul ignore … */ and /* c8 ignore … */ block comments written as JSX children on the generated component children getter. Line comments are not carried.

@solidjs/diagnostics@2.0.0-rc.14

Patch Changes

  • Updated dependencies [ecb68a1]
  • Updated dependencies [d4b10b5]
  • Updated dependencies [da84bd9]
  • Updated dependencies [2656284]
  • Updated dependencies [b0c8489]
  • Updated dependencies [8d66ae5]
    • @solidjs/web@2.0.0-rc.14
    • @solidjs/signals@2.0.0-rc.14
    • solid-js@2.0.0-rc.14

@solidjs/element@2.0.0-rc.14

Patch Changes

  • Updated dependencies [ecb68a1]
  • Updated dependencies [d4b10b5]
  • Updated dependencies [da84bd9]
  • Updated dependencies [2656284]
  • Updated dependencies [8d66ae5]
    • @solidjs/web@2.0.0-rc.14
    • solid-js@2.0.0-rc.14

@solidjs/h@2.0.0-rc.14

Patch Changes

  • ecb68a1: Binding slots: the fill runs once per occurrence, untracked, under the occurrence's owner — as a component body and a template-slot fill do. State created in the fill lives as long as the occurrence; a top-level read is a one-time read (dev: STRICT_READ_UNTRACKED, naming the fill); getters are the reactive form. Handlers and refs are read once when an element binds and go through assign, so events delegate, tuples bind and interactions wrap as in client JSX. On the server an array at a handler position is a dev finding (reason tuple) instead of being flattened; only ref merges arrays. Template-slot fills are untracked on every render path and carry the same labelled warning.

    Breaking: AttributeSlot is renamed BindingSlot, with no alias, and its return is constrained (SlotOutput<J> / SlotError<M>, both exported) so an array, DOM node, function, async value or $-prefixed key is a type error on both sides. The diagnostic code ATTRIBUTE_SLOT_POSITION is renamed BINDING_SLOT_POSITION. The fill-shape finding also names async values.

  • Updated dependencies [ecb68a1]

  • Updated dependencies [d4b10b5]

  • Updated dependencies [2656284]

  • Updated dependencies [8d66ae5]

    • @solidjs/web@2.0.0-rc.14

@solidjs/html@2.0.0-rc.14

Patch Changes

  • Updated dependencies [ecb68a1]
  • Updated dependencies [d4b10b5]
  • Updated dependencies [2656284]
  • Updated dependencies [8d66ae5]
    • @solidjs/web@2.0.0-rc.14

@solidjs/signals@2.0.0-rc.14

Patch Changes

  • ecb68a1: Binding slots: the fill runs once per occurrence, untracked, under the occurrence's owner — as a component body and a template-slot fill do. State created in the fill lives as long as the occurrence; a top-level read is a one-time read (dev: STRICT_READ_UNTRACKED, naming the fill); getters are the reactive form. Handlers and refs are read once when an element binds and go through assign, so events delegate, tuples bind and interactions wrap as in client JSX. On the server an array at a handler position is a dev finding (reason tuple) instead of being flattened; only ref merges arrays. Template-slot fills are untracked on every render path and carry the same labelled warning.

    Breaking: AttributeSlot is renamed BindingSlot, with no alias, and its return is constrained (SlotOutput<J> / SlotError<M>, both exported) so an array, DOM node, function, async value or $-prefixed key is a type error on both sides. The diagnostic code ATTRIBUTE_SLOT_POSITION is renamed BINDING_SLOT_POSITION. The fill-shape finding also names async values.

  • b0c8489: A re-run that commits undefined is no longer counted as waste. A projection that mutates its draft or reconciles a returned value, or a memo that does its work by writing a signal, has no output to compare, so its re-runs were reported as pure cost. RerunEvent.changed now reports true for these runs (as it already did for side-effect-only effects), so WASTED_RECOMPUTE no longer fires for them and costs().wastedMs, expectNoWaste and the performance tracks stop counting them as wasted.

solid-js@2.0.0-rc.14

Patch Changes

  • da84bd9: Fix hydration adoption throwing when a traced compute calls Promise.withResolvers() or Promise.try(). The trace run swaps the global Promise for a never-settling mock that lacked these two statics, so the call threw out of hydration instead of adopting the server value. The mock now provides both: withResolvers returns a never-settling mock with no-op resolve/reject, and try returns a never-settling mock without invoking its callback (matching how the mock's constructor ignores its executor).
  • Updated dependencies [ecb68a1]
  • Updated dependencies [b0c8489]
    • @solidjs/signals@2.0.0-rc.14

@solidjs/universal@2.0.0-rc.14

Patch Changes

  • Updated dependencies [da84bd9]
    • solid-js@2.0.0-rc.14

@solidjs/web@2.0.0-rc.14

Patch Changes

  • ecb68a1: Binding slots: the fill runs once per occurrence, untracked, under the occurrence's owner — as a component body and a template-slot fill do. State created in the fill lives as long as the occurrence; a top-level read is a one-time read (dev: STRICT_READ_UNTRACKED, naming the fill); getters are the reactive form. Handlers and refs are read once when an element binds and go through assign, so events delegate, tuples bind and interactions wrap as in client JSX. On the server an array at a handler position is a dev finding (reason tuple) instead of being flattened; only ref merges arrays. Template-slot fills are untracked on every render path and carry the same labelled warning.

    Breaking: AttributeSlot is renamed BindingSlot, with no alias, and its return is constrained (SlotOutput<J> / SlotError<M>, both exported) so an array, DOM node, function, async value or $-prefixed key is a type error on both sides. The diagnostic code ATTRIBUTE_SLOT_POSITION is renamed BINDING_SLOT_POSITION. The fill-shape finding also names async values.

  • d4b10b5: Binding slots: a slot property placed as a child (<strong>{list.remaining}</strong> items left) is a text position. The server emits a comment pair around it, <!--_s:t=<occurrence>:<key>-->…<!--/_s:t-->, with the escaped t=0 value inside on the document face and nothing on the stream face; the client writes the text between the markers from the occurrence's render effect, and a refetch's morph keeps the client's text. Strings and numbers render; nullish and booleans render empty, as a client insert renders them. Any other value is a new client dev finding (BINDING_SLOT_POSITION, reason text-shape) and clears. The content of <textarea>, <title>, <style> and <script> is not a text position (a comment is literal text there); bind value= or a style property instead.

    Breaking: a slot property as a child used to render nothing and raise the text finding; it now renders and binds, and the text reason is retired.

  • 2656284: createSSRResponse no longer hangs when a streamed render ends before its shell flushes ([2.0 rc.11] createSSRResponse never settles when the render fails before the shell flushes #3719). A render that fails pre-shell (onError hears handling: "failed") or is aborted through its signal now resolves with a bodyless 500, or a redirect when a Location is already on the response stub, and the stub is committed. A render that succeeds with an empty document resolves with an empty 200. The promise still never rejects.

  • 8d66ae5: Server bundles that don't serialize no longer retain the serializer's plugin set. Five module-level statements that Rollup shakes but Rolldown (Vite) and esbuild keep are now side-effect free to every bundler: the frozen DEFAULT_WEB_PLUGINS array is /* @__PURE__ */-annotated, seroval Feature flags are read on use, the stub gap-fill header set is built on first use, the event-stream heartbeat's new TextEncoder() is annotated (and no longer built at import time by dist/server.js), and the flash-cookie matcher is a regex literal. A server bundle importing only isServer or getRequestEvent drops from ~11.7 KB to ~1.6 KB minified (seroval bundled; Rolldown), and renderToString bundles shed ~260–380 B. No behavior or API change.

  • Updated dependencies [da84bd9]

    • solid-js@2.0.0-rc.14

todos-server-example@0.0.1-rc.2

Patch Changes

  • Updated dependencies [ecb68a1]
  • Updated dependencies [d4b10b5]
  • Updated dependencies [da84bd9]
  • Updated dependencies [2656284]
  • Updated dependencies [8d66ae5]
    • @solidjs/web@2.0.0-rc.14
    • solid-js@2.0.0-rc.14

test-integration@2.0.0-rc.14

Patch Changes

  • Updated dependencies [ecb68a1]
  • Updated dependencies [d4b10b5]
  • Updated dependencies [3c1f809]
  • Updated dependencies [da84bd9]
  • Updated dependencies [2656284]
  • Updated dependencies [b0c8489]
  • Updated dependencies [8d66ae5]
    • @solidjs/web@2.0.0-rc.14
    • @solidjs/signals@2.0.0-rc.14
    • @solidjs/h@2.0.0-rc.14
    • @solidjs/babel-plugin@2.0.0-rc.14
    • solid-js@2.0.0-rc.14
    • @solidjs/html@2.0.0-rc.14
    • @solidjs/universal@2.0.0-rc.14

@github-actions
github-actions Bot force-pushed the changeset-release/next branch 8 times, most recently from 441ec34 to 4af8f17 Compare September 30, 2026 19:28
@github-actions
github-actions Bot force-pushed the changeset-release/next branch from 4af8f17 to f398110 Compare September 30, 2026 20:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants