Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 0 additions & 6 deletions .changeset/change-multi-statement.md

This file was deleted.

6 changes: 0 additions & 6 deletions .changeset/change-parse-failures.md

This file was deleted.

8 changes: 0 additions & 8 deletions .changeset/init-db-layout-agent-files.md

This file was deleted.

8 changes: 0 additions & 8 deletions .changeset/update-skill-prompt.md

This file was deleted.

10 changes: 10 additions & 0 deletions examples/llm-memory-db-mssql/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -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
Expand Down
2 changes: 1 addition & 1 deletion examples/llm-memory-db-mssql/package.json
Original file line number Diff line number Diff line change
@@ -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",
Expand Down
10 changes: 10 additions & 0 deletions examples/llm-memory-db-pg/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -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
Expand Down
2 changes: 1 addition & 1 deletion examples/llm-memory-db-pg/package.json
Original file line number Diff line number Diff line change
@@ -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",
Expand Down
10 changes: 10 additions & 0 deletions examples/todo-db/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -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
Expand Down
2 changes: 1 addition & 1 deletion examples/todo-db/package.json
Original file line number Diff line number Diff line change
@@ -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",
Expand Down
17 changes: 17 additions & 0 deletions packages/cli/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -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 <name>` 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
Expand Down
2 changes: 1 addition & 1 deletion packages/cli/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@noormdev/cli",
"version": "1.5.1",
"version": "1.6.0",
"description": "Database schema & changeset manager CLI",
"type": "module",
"bin": {
Expand Down
17 changes: 17 additions & 0 deletions packages/sdk/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -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 <name>` 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
Expand Down
2 changes: 1 addition & 1 deletion packages/sdk/package.json
Original file line number Diff line number Diff line change
@@ -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",
Expand Down