reylo-effect 0.5.0 → 0.5.1

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 0.5.1 — 2026-10-26
+
+### Added
+
+- Workspace members inherit the workspace root's `.reylo.yaml`. A package listed by `workspaces` in the root `package.json` (npm, Yarn, Bun) or by `pnpm-workspace.yaml` that has no project file of its own now searches past its `package.json` up to the workspace root, so one root file (for example `schema: [migrations/*.sql]`) configures every member without per-package copies or `REYLO_CONFIG`. A member's own or nested `.reylo.yaml` still wins, and the content mapper watches each directory up to the root for one being added.
+
 ## 0.5.0 — 2026-10-26
 
 ### Breaking

package/README.md

@@ -102,6 +102,19 @@ direct_url: postgres://localhost/app
 
 Analysis results are cached in `.reylo/` and refreshed when SQL or schema changes. Analysis never migrates the application database.
 
+### Workspaces
+
+A query uses the nearest `.reylo.yaml` at or above it, up to its package's `package.json`. A workspace member — a package that `workspaces` in the root `package.json` (npm, Yarn, Bun) or `pnpm-workspace.yaml` lists — keeps looking up to the workspace root, so one root file configures every member:
+
+```yaml
+# .reylo.yaml at the workspace root
+schema:
+  - migrations/*.sql
+direct_url: file:./dev.db
+```
+
+Paths in it resolve from the root, and `.reylo/` is written there. A `.reylo.yaml` inside a member, or nested deeper, still configures the queries under it. Engines and SQLite drivers are read from the root `package.json`.
+
 ### Migrations
 
 `migrate(directory)` from `reylo-effect` applies pending `N_name.sql` files in numeric order and records them in `reylo_migrations`. Provide the SQL client and `NodeServices.layer`, as in the quick start.

package/SPEC.md

@@ -267,6 +267,8 @@ The unbundled loader is `node --import reylo-effect/register`. It resolves and l
 
 Deployment modes are in [section 2.2](#22-deployment-modes).
 
+A query's project file is the nearest `.reylo.yaml` or `.reylo.yml` at or above its directory, searched up to its package's `package.json`. A workspace member — a package listed by `workspaces` in its workspace root's `package.json` (npm and Bun patterns, or Yarn's `{ packages }`) or by `packages` in `pnpm-workspace.yaml`, after `!` exclusions — searches on up to that root; the nearest directory declaring a workspace is the root, and a `pnpm-workspace.yaml` there takes precedence over `package.json`. The file found configures the queries below it as its own directory's project: relative paths, `.env` files, and `.reylo/` resolve from that directory, and the engines and SQLite drivers its `package.json` lists apply. `REYLO_CONFIG` names one file for every query.
+
 The analysis URL is `direct_url` in `.reylo.yaml`, else `DATABASE_URL`. With a URL, a session reads the schema fingerprint and analyzes live, falling back to `.reylo/` when the database cannot be reached. Cache-only analysis — `REYLO_OFFLINE=1` in the environment or `offline: true` in `.reylo.yaml`; the environment wins, and `REYLO_OFFLINE=0` turns it off — never opens a connection, not even for the fingerprint, and answers from `.reylo/` entries alone. A statement with no entry fails its import with a diagnostic that names the file. Schema-file sessions in cache-only mode read the schema files for their fingerprint but never load them into a database. Native JSON arguments need parameter descriptions that are not cached, so they fail in cache-only mode.
 
 Production `register` deployments analyze in CI against a dedicated analysis database (populating `.reylo/`), ship `.reylo/` with the application, and run with `REYLO_OFFLINE=1`. A deployment that wants live analysis sets `direct_url` to a dedicated analysis database rather than relying on a production `DATABASE_URL`.

package/dist/esbuild.js

@@ -1,5 +1,5 @@
 // src/tooling.ts
-var TOOLING_VERSION = "0.5.0";
+var TOOLING_VERSION = "0.5.1";
 async function loadTooling(entry, load) {
   try {
     return await load();

package/dist/mapper.js

@@ -1,5 +1,5 @@
 // src/tooling.ts
-var TOOLING_VERSION = "0.5.0";
+var TOOLING_VERSION = "0.5.1";
 async function loadTooling(entry, load) {
   try {
     return await load();

package/dist/register.js

@@ -1,5 +1,5 @@
 // src/tooling.ts
-var TOOLING_VERSION = "0.5.0";
+var TOOLING_VERSION = "0.5.1";
 async function loadTooling(entry, load) {
   try {
     return await load();

package/dist/vite.js

@@ -1,5 +1,5 @@
 // src/tooling.ts
-var TOOLING_VERSION = "0.5.0";
+var TOOLING_VERSION = "0.5.1";
 async function loadTooling(entry, load) {
   try {
     return await load();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "reylo-effect",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "description": "Import .sql files as Effect queries checked against SQLite, Postgres, or MySQL.",
   "license": "MIT",
   "workspaces": [
@@ -83,7 +83,7 @@
   },
   "peerDependencies": {
     "@effect/sql-d1": "4.0.6",
-    "reylo-effect-tooling": "0.5.0",
+    "reylo-effect-tooling": "0.5.1",
     "vite": ">=8.0.0 <9.0.0"
   },
   "peerDependenciesMeta": {