Skip to content

Release RC packages (rc) - #4683

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 Nov 4, 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/diagnostics@2.0.0-rc.22

Patch Changes

  • Updated dependencies [f6b6737]
  • Updated dependencies [5208944]
  • Updated dependencies [6b7474b]
  • Updated dependencies [4fe7532]
  • Updated dependencies [fb672ca]
    • @solidjs/signals@2.0.0-rc.22
    • @solidjs/web@2.0.0-rc.22
    • solid-js@2.0.0-rc.22

@solidjs/element@2.0.0-rc.22

Patch Changes

  • @solidjs/web@2.0.0-rc.22
  • solid-js@2.0.0-rc.22

@solidjs/h@2.0.0-rc.22

Patch Changes

  • @solidjs/web@2.0.0-rc.22

@solidjs/html@2.0.0-rc.22

Patch Changes

  • @solidjs/web@2.0.0-rc.22

@solidjs/signals@2.0.0-rc.22

Patch Changes

  • f6b6737: Add DEV.setSignal so development tooling can write signal values and store property slots (Add DEV.setSignal so devtools can write a signal or store node #4679).

  • 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 an isPending(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).

    • When the memo's lane landed in the same seam as the write it reads ahead of, the landing voided the binding's lane run, so the memo's pending: true showed while the binding stayed false. The lane now reveals whole (F-6), and the landing's re-derivation follows next round.
    • When the lane landed first, the write's landing re-derived the memo onto a new flight and held its own runs for it, but that flush's runs of effects deriving plainly from the landing still ran: details: Item 1 showed beside id: 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 a createOptimisticStore keyed, 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's refresh() 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.

  • fb672ca: IMMUTABLE_UPDATE_IN_STORE no longer reports wholesale replacements on a shallow store, or of a markRaw / 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

  • Updated dependencies [f6b6737]
  • Updated dependencies [5208944]
  • Updated dependencies [6b7474b]
  • Updated dependencies [4fe7532]
  • Updated dependencies [fb672ca]
    • @solidjs/signals@2.0.0-rc.22

@solidjs/universal@2.0.0-rc.22

Patch Changes

  • solid-js@2.0.0-rc.22

@solidjs/web@2.0.0-rc.22

Patch Changes

  • solid-js@2.0.0-rc.22

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

@solidjs/compiler@2.0.0-rc.22

board-example@0.0.1-rc.7

Patch Changes

  • @solidjs/web@2.0.0-rc.22
  • solid-js@2.0.0-rc.22

canvas-example@0.0.1-rc.3

Patch Changes

  • @solidjs/web@2.0.0-rc.22
  • solid-js@2.0.0-rc.22

server-dbmon-example@0.0.1-rc.6

Patch Changes

  • @solidjs/web@2.0.0-rc.22
  • solid-js@2.0.0-rc.22

todos-server-example@0.0.1-rc.10

Patch Changes

  • @solidjs/web@2.0.0-rc.22
  • solid-js@2.0.0-rc.22

test-integration@2.0.0-rc.22

Patch Changes

  • Updated dependencies [f6b6737]
  • Updated dependencies [5208944]
  • Updated dependencies [6b7474b]
  • Updated dependencies [4fe7532]
  • Updated dependencies [fb672ca]
    • @solidjs/signals@2.0.0-rc.22
    • @solidjs/web@2.0.0-rc.22
    • solid-js@2.0.0-rc.22
    • @solidjs/babel-plugin@2.0.0-rc.22
    • @solidjs/html@2.0.0-rc.22
    • @solidjs/h@2.0.0-rc.22
    • @solidjs/universal@2.0.0-rc.22

@github-actions
github-actions Bot force-pushed the changeset-release/next branch 4 times, most recently from b3d6b74 to 720678d Compare November 5, 2026 20:09
@github-actions
github-actions Bot force-pushed the changeset-release/next branch from 720678d to f8fa234 Compare November 6, 2026 05:27
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