From c04ab63ce152bcc566dc2177b820d720c2475440 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Fri, 23 Oct 2026 04:41:10 +0000 Subject: [PATCH] Version Packages --- .changeset/change-multi-statement.md | 6 ------ .changeset/change-parse-failures.md | 6 ------ .changeset/init-db-layout-agent-files.md | 8 -------- .changeset/update-skill-prompt.md | 8 -------- examples/llm-memory-db-mssql/CHANGELOG.md | 10 ++++++++++ examples/llm-memory-db-mssql/package.json | 2 +- examples/llm-memory-db-pg/CHANGELOG.md | 10 ++++++++++ examples/llm-memory-db-pg/package.json | 2 +- examples/todo-db/CHANGELOG.md | 10 ++++++++++ examples/todo-db/package.json | 2 +- packages/cli/CHANGELOG.md | 17 +++++++++++++++++ packages/cli/package.json | 2 +- packages/sdk/CHANGELOG.md | 17 +++++++++++++++++ packages/sdk/package.json | 2 +- 14 files changed, 69 insertions(+), 33 deletions(-) delete mode 100644 .changeset/change-multi-statement.md delete mode 100644 .changeset/change-parse-failures.md delete mode 100644 .changeset/init-db-layout-agent-files.md delete mode 100644 .changeset/update-skill-prompt.md diff --git a/.changeset/change-multi-statement.md b/.changeset/change-multi-statement.md deleted file mode 100644 index 341abd80..00000000 --- a/.changeset/change-multi-statement.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -'@noormdev/cli': patch -'@noormdev/sdk': patch ---- - -A change file with more than one statement now runs every statement on SQLite, and `GO` batch separators in change files are honored on SQL Server, as they already were for `sql/` files. Before, SQLite ran only the first statement of a change file and reported success. diff --git a/.changeset/change-parse-failures.md b/.changeset/change-parse-failures.md deleted file mode 100644 index 0d070d9d..00000000 --- a/.changeset/change-parse-failures.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -'@noormdev/cli': patch -'@noormdev/sdk': patch ---- - -`noorm change ff` and `change next` now fail at the position of a change folder that cannot be parsed when they would run it (never run, `reverted`, or `stale`), for example a `.txt` manifest that names a file no longer in `sql/`. Before, the folder was skipped, later changes ran without it, and the command exited 0. `change list` shows such a change as `failed` with the parse error, the TUI change screens and home count include it, `changes.pending()` returns it, and `change run ` reports the parse error instead of "Change not found". An applied change keeps its status, and the batch adds a warning instead of failing. A folder with neither `change/` nor `revert/` is not a change and is ignored. diff --git a/.changeset/init-db-layout-agent-files.md b/.changeset/init-db-layout-agent-files.md deleted file mode 100644 index 2154b20b..00000000 --- a/.changeset/init-db-layout-agent-files.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -'@noormdev/cli': minor -'@noormdev/sdk': minor ---- - -`noorm init` now creates `db/sql/` and `db/changes/` instead of `sql/` and `changes/`, and writes `db/AGENTS.md` and `db/CLAUDE.md`. `AGENTS.md` points coding agents at the `/noorm` skill and points data modeling at ignatius and its `/ignatius-modeling` skill. It also leaves a marker for your own steering. `CLAUDE.md` imports `AGENTS.md`. Neither file is overwritten on re-init. Overwriting a settings file (`noorm init --force`, `noorm settings init --force`) keeps the `paths` already in it. The `noorm` skill now states what `sql/` and `changes/` are for, which edits belong in each, how to reference `sql/` files from a change with a `.txt` manifest, and when to use a `.sql.tmpl`. - -The built-in default for `paths.sql` and `paths.changes` is now `./db/sql` and `./db/changes`, matching what `noorm init` creates. `noorm init` writes `paths` into `settings.yml`, so an initialized project keeps its layout. A project laid out at `./sql` and `./changes` whose `settings.yml` is missing, empty, or has no `paths` key now resolves to `./db/sql` and `./db/changes`. Add `paths: { sql: ./sql, changes: ./changes }` to `settings.yml`, or set `NOORM_PATHS_SQL` and `NOORM_PATHS_CHANGES`. diff --git a/.changeset/update-skill-prompt.md b/.changeset/update-skill-prompt.md deleted file mode 100644 index a54276de..00000000 --- a/.changeset/update-skill-prompt.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -'@noormdev/cli': minor -'@noormdev/sdk': minor ---- - -After a successful update, `noorm update` offers the noorm agent skill. It runs `npx skills add noormdev/noorm/skills` when `npx` is on `PATH`, else `gh skill install noormdev/noorm skills/noorm` (GitHub CLI 2.90 or newer). With neither, or when the command fails, it prints both commands and where to get Node.js and the GitHub CLI. On a terminal it asks first; piped output prints the command instead, and `--json` skips the offer. A declined or failed skill install does not change the exit code. - -On a terminal, `noorm update` now rewrites its status line in place: `Checking for updates...` is replaced by the result, and the download counter ends on `Downloaded X MB (100%)`. `noorm update --json` now writes only the JSON document to stdout; before, status lines preceded it. diff --git a/examples/llm-memory-db-mssql/CHANGELOG.md b/examples/llm-memory-db-mssql/CHANGELOG.md index 03a41957..77096d52 100644 --- a/examples/llm-memory-db-mssql/CHANGELOG.md +++ b/examples/llm-memory-db-mssql/CHANGELOG.md @@ -1,5 +1,15 @@ # @noormdev/example-llm-memory-db-mssql +## 0.0.12 + +### Patch Changes + +- Updated dependencies [6dbc2e3] +- Updated dependencies [6dbc2e3] +- Updated dependencies [d497028] +- Updated dependencies [6dbc2e3] + - @noormdev/sdk@1.6.0 + ## 0.0.11 ### Patch Changes diff --git a/examples/llm-memory-db-mssql/package.json b/examples/llm-memory-db-mssql/package.json index fa936653..befbfa92 100644 --- a/examples/llm-memory-db-mssql/package.json +++ b/examples/llm-memory-db-mssql/package.json @@ -1,6 +1,6 @@ { "name": "@noormdev/example-llm-memory-db-mssql", - "version": "0.0.11", + "version": "0.0.12", "private": true, "type": "module", "description": "LLM-memory schema + SDK example exercising NoORM against MSSQL with TVPs", diff --git a/examples/llm-memory-db-pg/CHANGELOG.md b/examples/llm-memory-db-pg/CHANGELOG.md index 9b026644..b5221e59 100644 --- a/examples/llm-memory-db-pg/CHANGELOG.md +++ b/examples/llm-memory-db-pg/CHANGELOG.md @@ -1,5 +1,15 @@ # @noormdev/example-llm-memory-db-pg +## 0.0.12 + +### Patch Changes + +- Updated dependencies [6dbc2e3] +- Updated dependencies [6dbc2e3] +- Updated dependencies [d497028] +- Updated dependencies [6dbc2e3] + - @noormdev/sdk@1.6.0 + ## 0.0.11 ### Patch Changes diff --git a/examples/llm-memory-db-pg/package.json b/examples/llm-memory-db-pg/package.json index 64c37e13..80a1ae43 100644 --- a/examples/llm-memory-db-pg/package.json +++ b/examples/llm-memory-db-pg/package.json @@ -1,6 +1,6 @@ { "name": "@noormdev/example-llm-memory-db-pg", - "version": "0.0.11", + "version": "0.0.12", "private": true, "type": "module", "description": "Full-surface noorm example: LLM memory + task tracker schema, SDK, and tests against PostgreSQL", diff --git a/examples/todo-db/CHANGELOG.md b/examples/todo-db/CHANGELOG.md index f2bf738f..75f49015 100644 --- a/examples/todo-db/CHANGELOG.md +++ b/examples/todo-db/CHANGELOG.md @@ -1,5 +1,15 @@ # @noormdev/example-todo-db +## 0.0.12 + +### Patch Changes + +- Updated dependencies [6dbc2e3] +- Updated dependencies [6dbc2e3] +- Updated dependencies [d497028] +- Updated dependencies [6dbc2e3] + - @noormdev/sdk@1.6.0 + ## 0.0.11 ### Patch Changes diff --git a/examples/todo-db/package.json b/examples/todo-db/package.json index 02835bc2..d67b9e6f 100644 --- a/examples/todo-db/package.json +++ b/examples/todo-db/package.json @@ -1,6 +1,6 @@ { "name": "@noormdev/example-todo-db", - "version": "0.0.11", + "version": "0.0.12", "private": true, "type": "module", "description": "SDK integration tests exercising the todo-db example schema", diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.md index 244943ef..9fae18f7 100644 --- a/packages/cli/CHANGELOG.md +++ b/packages/cli/CHANGELOG.md @@ -1,5 +1,22 @@ # @noormdev/cli +## 1.6.0 + +### Minor Changes + +- d497028: `noorm init` now creates `db/sql/` and `db/changes/` instead of `sql/` and `changes/`, and writes `db/AGENTS.md` and `db/CLAUDE.md`. `AGENTS.md` points coding agents at the `/noorm` skill and points data modeling at ignatius and its `/ignatius-modeling` skill. It also leaves a marker for your own steering. `CLAUDE.md` imports `AGENTS.md`. Neither file is overwritten on re-init. Overwriting a settings file (`noorm init --force`, `noorm settings init --force`) keeps the `paths` already in it. The `noorm` skill now states what `sql/` and `changes/` are for, which edits belong in each, how to reference `sql/` files from a change with a `.txt` manifest, and when to use a `.sql.tmpl`. + + The built-in default for `paths.sql` and `paths.changes` is now `./db/sql` and `./db/changes`, matching what `noorm init` creates. `noorm init` writes `paths` into `settings.yml`, so an initialized project keeps its layout. A project laid out at `./sql` and `./changes` whose `settings.yml` is missing, empty, or has no `paths` key now resolves to `./db/sql` and `./db/changes`. Add `paths: { sql: ./sql, changes: ./changes }` to `settings.yml`, or set `NOORM_PATHS_SQL` and `NOORM_PATHS_CHANGES`. + +- 6dbc2e3: After a successful update, `noorm update` offers the noorm agent skill. It runs `npx skills add noormdev/noorm/skills` when `npx` is on `PATH`, else `gh skill install noormdev/noorm skills/noorm` (GitHub CLI 2.90 or newer). With neither, or when the command fails, it prints both commands and where to get Node.js and the GitHub CLI. On a terminal it asks first; piped output prints the command instead, and `--json` skips the offer. A declined or failed skill install does not change the exit code. + + On a terminal, `noorm update` now rewrites its status line in place: `Checking for updates...` is replaced by the result, and the download counter ends on `Downloaded X MB (100%)`. `noorm update --json` now writes only the JSON document to stdout; before, status lines preceded it. + +### Patch Changes + +- 6dbc2e3: A change file with more than one statement now runs every statement on SQLite, and `GO` batch separators in change files are honored on SQL Server, as they already were for `sql/` files. Before, SQLite ran only the first statement of a change file and reported success. +- 6dbc2e3: `noorm change ff` and `change next` now fail at the position of a change folder that cannot be parsed when they would run it (never run, `reverted`, or `stale`), for example a `.txt` manifest that names a file no longer in `sql/`. Before, the folder was skipped, later changes ran without it, and the command exited 0. `change list` shows such a change as `failed` with the parse error, the TUI change screens and home count include it, `changes.pending()` returns it, and `change run ` reports the parse error instead of "Change not found". An applied change keeps its status, and the batch adds a warning instead of failing. A folder with neither `change/` nor `revert/` is not a change and is ignored. + ## 1.5.1 ### Patch Changes diff --git a/packages/cli/package.json b/packages/cli/package.json index 922fbfb9..d6f40f82 100644 --- a/packages/cli/package.json +++ b/packages/cli/package.json @@ -1,6 +1,6 @@ { "name": "@noormdev/cli", - "version": "1.5.1", + "version": "1.6.0", "description": "Database schema & changeset manager CLI", "type": "module", "bin": { diff --git a/packages/sdk/CHANGELOG.md b/packages/sdk/CHANGELOG.md index 0e2d300a..6c4f707f 100644 --- a/packages/sdk/CHANGELOG.md +++ b/packages/sdk/CHANGELOG.md @@ -1,5 +1,22 @@ # @noormdev/sdk +## 1.6.0 + +### Minor Changes + +- d497028: `noorm init` now creates `db/sql/` and `db/changes/` instead of `sql/` and `changes/`, and writes `db/AGENTS.md` and `db/CLAUDE.md`. `AGENTS.md` points coding agents at the `/noorm` skill and points data modeling at ignatius and its `/ignatius-modeling` skill. It also leaves a marker for your own steering. `CLAUDE.md` imports `AGENTS.md`. Neither file is overwritten on re-init. Overwriting a settings file (`noorm init --force`, `noorm settings init --force`) keeps the `paths` already in it. The `noorm` skill now states what `sql/` and `changes/` are for, which edits belong in each, how to reference `sql/` files from a change with a `.txt` manifest, and when to use a `.sql.tmpl`. + + The built-in default for `paths.sql` and `paths.changes` is now `./db/sql` and `./db/changes`, matching what `noorm init` creates. `noorm init` writes `paths` into `settings.yml`, so an initialized project keeps its layout. A project laid out at `./sql` and `./changes` whose `settings.yml` is missing, empty, or has no `paths` key now resolves to `./db/sql` and `./db/changes`. Add `paths: { sql: ./sql, changes: ./changes }` to `settings.yml`, or set `NOORM_PATHS_SQL` and `NOORM_PATHS_CHANGES`. + +- 6dbc2e3: After a successful update, `noorm update` offers the noorm agent skill. It runs `npx skills add noormdev/noorm/skills` when `npx` is on `PATH`, else `gh skill install noormdev/noorm skills/noorm` (GitHub CLI 2.90 or newer). With neither, or when the command fails, it prints both commands and where to get Node.js and the GitHub CLI. On a terminal it asks first; piped output prints the command instead, and `--json` skips the offer. A declined or failed skill install does not change the exit code. + + On a terminal, `noorm update` now rewrites its status line in place: `Checking for updates...` is replaced by the result, and the download counter ends on `Downloaded X MB (100%)`. `noorm update --json` now writes only the JSON document to stdout; before, status lines preceded it. + +### Patch Changes + +- 6dbc2e3: A change file with more than one statement now runs every statement on SQLite, and `GO` batch separators in change files are honored on SQL Server, as they already were for `sql/` files. Before, SQLite ran only the first statement of a change file and reported success. +- 6dbc2e3: `noorm change ff` and `change next` now fail at the position of a change folder that cannot be parsed when they would run it (never run, `reverted`, or `stale`), for example a `.txt` manifest that names a file no longer in `sql/`. Before, the folder was skipped, later changes ran without it, and the command exited 0. `change list` shows such a change as `failed` with the parse error, the TUI change screens and home count include it, `changes.pending()` returns it, and `change run ` reports the parse error instead of "Change not found". An applied change keeps its status, and the batch adds a warning instead of failing. A folder with neither `change/` nor `revert/` is not a change and is ignored. + ## 1.5.1 ### Patch Changes diff --git a/packages/sdk/package.json b/packages/sdk/package.json index 1de9afbc..e259bfce 100644 --- a/packages/sdk/package.json +++ b/packages/sdk/package.json @@ -1,6 +1,6 @@ { "name": "@noormdev/sdk", - "version": "1.5.1", + "version": "1.6.0", "description": "Database schema & changeset manager SDK", "type": "module", "main": "./dist/index.js",