From 768e5179edd34898170b70e3b44f9d6690f33b34 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Fri, 21 Aug 2026 15:05:05 +0000
Subject: [PATCH] chore: update versions (beta)

---
 .changeset/pre.json | 1 +
 CHANGELOG.md        | 8 ++++++++
 package.json        | 2 +-
 3 files changed, 10 insertions(+), 1 deletion(-)

diff --git a/.changeset/pre.json b/.changeset/pre.json
index 89a4a29..c2a726d 100644
--- a/.changeset/pre.json
+++ b/.changeset/pre.json
@@ -29,6 +29,7 @@
     "polite-geckos-perform",
     "polite-heads-walk",
     "poor-olives-peel",
+    "quick-fragments-sync",
     "silver-cases-heal",
     "silver-paws-push",
     "tasty-deers-think",
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8103f8b..619f553 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,13 @@
 # solid-relay
 
+## 1.0.0-beta.28
+
+### Patch Changes
+
+- 996e806: fix: publish fragment results synchronously
+
+  `createFragment` deferred every `observeFragment` result to a microtask, including the first snapshot emitted synchronously on subscribe for data already in the store. Nested fragment components therefore needed one microtask turn per level, and when mounted inside a pending Solid transition (e.g. a router navigation) each level's gating memo was computed on both the normal and the transition branch, re-creating the subtree `2^depth - 1` times. Results are now published synchronously, and the underlying resource resolves immediately for data already in the store instead of becoming pending.
+
 ## 1.0.0-beta.27
 
 ### Patch Changes
diff --git a/package.json b/package.json
index 5f37d06..7250565 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
 	"name": "solid-relay",
-	"version": "1.0.0-beta.27",
+	"version": "1.0.0-beta.28",
 	"description": "SolidJS bindings for Relay",
 	"homepage": "https://solid-relay.xiniha.dev",
 	"license": "MIT",