From 5b7a7e49aeedb00cad4fd63bd6d0f41107e87de2 Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 19 Jun 2026 18:15:18 +0000 Subject: [PATCH 1/2] Sort "Built migrations:" CLI output by filename The build-db-migrations command printed the built migrations in Bun's bundler output order, which is not guaranteed to be sorted. Since migrations apply in lexicographic filename order, the unsorted summary could misrepresent the actual apply order. Sort a copy of the build outputs by filename before printing so the summary is deterministic and reflects apply order. Co-Authored-By: Claude Opus 4.8 Claude-Session: https://claude.ai/code/session_012Y2mvzwhEWcWZxiHMTsrW8 --- src/build-db-migrations.ts | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/src/build-db-migrations.ts b/src/build-db-migrations.ts index 0b56716..91fd0e1 100644 --- a/src/build-db-migrations.ts +++ b/src/build-db-migrations.ts @@ -189,10 +189,13 @@ buildDbMigrations } } - // Print summary + // Print summary (sorted by filename — this is the order migrations apply in) console.log(""); console.log("Built migrations:"); - for (const migration of migrationsResult.outputs) { + const sortedOutputs = [...migrationsResult.outputs].sort((a, b) => + basename(a.path).localeCompare(basename(b.path)), + ); + for (const migration of sortedOutputs) { console.log(` - ${basename(migration.path)} (${migration.size} bytes)`); } console.log(""); From a19225549726461ca2bcdaa34cc7c1602c946027 Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 19 Jun 2026 18:21:56 +0000 Subject: [PATCH 2/2] Bump version to 0.11.2 and sync README Bump the package version following the addition of sorted CLI migration output, and update the README body copy so the documented npm package / ws-proxy image version matches package.json. Co-Authored-By: Claude Opus 4.8 Claude-Session: https://claude.ai/code/session_012Y2mvzwhEWcWZxiHMTsrW8 --- README.md | 2 +- package.json | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index fc581fe..e7d94a7 100644 --- a/README.md +++ b/README.md @@ -20,7 +20,7 @@ Ensure that you have both `postgres` and a `postgres-ws-proxy` containers runnin You'll likely want to replace the `build:` sections for the services in the e2e test example `.yml` file with `image:`. For example, use `image: postgres:17.7` for the `postgres` service. For the proxy, you can pull the docker image from `ghcr.io/schemavaults/dbh/postgres-ws-proxy`; use the version number equal to your `@schemavaults/dbh` npm package installation: ```md -# NPM Package: @schemavaults/dbh@0.11.1 => ghcr.io/schemavaults/dbh/postgres-ws-proxy:0.11.1 +# NPM Package: @schemavaults/dbh@0.11.2 => ghcr.io/schemavaults/dbh/postgres-ws-proxy:0.11.2 ``` ### In your application server code diff --git a/package.json b/package.json index 2ba9969..72e904d 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@schemavaults/dbh", - "version": "0.11.1", + "version": "0.11.2", "description": "Easily connect to PostgresDB from serverless environment", "license": "UNLICENSED", "private": false,