From 19c72cc02f3b49608d8e2efdc7a8c438b0cdfc35 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Thu, 24 Sep 2026 08:22:14 +0000
Subject: [PATCH] chore: release

---
 .changeset/server-function-pages.md | 5 -----
 CHANGELOG.md                        | 6 ++++++
 package.json                        | 2 +-
 3 files changed, 7 insertions(+), 6 deletions(-)
 delete mode 100644 .changeset/server-function-pages.md

diff --git a/.changeset/server-function-pages.md b/.changeset/server-function-pages.md
deleted file mode 100644
index 1040733..0000000
--- a/.changeset/server-function-pages.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"filesystem-routing": minor
----
-
-Server-function pages, behind `serverComponents: true`: a route module whose default export begins with a `"use server"` directive is flagged `server: true` and its `$component` ref marked `eager` (picking only `default`), so the Vite adapter delivers the stub as a static import even with code splitting on and it is not a build input. A new `filesystem-routing/flags` module exposes scan facts (`serverRoutes`) for emission adapters to gate static imports on: the shipped file says `true`; the Vite plugin serves the scan's answer in builds, folded to a literal, so gated code tree-shakes out of apps with no server page. `ModuleRef.eager` and `RouteManifestEntry.server` are added to the neutral manifest; `analyzeRouteModule` returns the default export's directive alongside the exports. Off by default: existing manifests are unchanged.
diff --git a/CHANGELOG.md b/CHANGELOG.md
index da49980..242c29a 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,11 @@
 # filesystem-routing
 
+## 0.4.0
+
+### Minor Changes
+
+- 4d628e2: Server-function pages, behind `serverComponents: true`: a route module whose default export begins with a `"use server"` directive is flagged `server: true` and its `$component` ref marked `eager` (picking only `default`), so the Vite adapter delivers the stub as a static import even with code splitting on and it is not a build input. A new `filesystem-routing/flags` module exposes scan facts (`serverRoutes`) for emission adapters to gate static imports on: the shipped file says `true`; the Vite plugin serves the scan's answer in builds, folded to a literal, so gated code tree-shakes out of apps with no server page. `ModuleRef.eager` and `RouteManifestEntry.server` are added to the neutral manifest; `analyzeRouteModule` returns the default export's directive alongside the exports. Off by default: existing manifests are unchanged.
+
 ## 0.3.1
 
 ### Patch Changes
diff --git a/package.json b/package.json
index fa41b63..18cec8a 100644
--- a/package.json
+++ b/package.json
@@ -2,7 +2,7 @@
   "name": "filesystem-routing",
   "description": "Router-neutral file-system routing: scans a route directory into a neutral route manifest with pluggable conventions and delivery adapters",
   "license": "MIT",
-  "version": "0.3.1",
+  "version": "0.4.0",
   "author": "Ryan Carniato",
   "homepage": "https://github.com/solidjs/filesystem-routing#readme",
   "repository": {