@izumisy/kyrage@1.5.8

Patch Changes

• #197 26695c5 Thanks @dependabot! - Updated better-sqlite3 (^12.4.1 -> ^12.6.2)

• #198 1371d2b Thanks @dependabot! - Updated sql-formatter (^15.6.12 -> ^15.7.0)

@izumisy/kyrage@1.5.7

Patch Changes

• #190 af17197 Thanks @dependabot! - Updated kysely (^0.28.8 -> ^0.28.9)

• #193 d5dfe5e Thanks @dependabot! - Updated sql-formatter (^15.6.10 -> ^15.6.12)

@izumisy/kyrage@1.5.6

Patch Changes

• #183 752db7c Thanks @dependabot! - Updated zod (^4.1.12 -> ^4.3.5)

• #175 2a3a379 Thanks @dependabot! - Bump vitest from 3.2.4 to 4.0.16

@izumisy/kyrage@1.5.5

Patch Changes

• #179 4ea9edf Thanks @IzumiSy! - Use Node.js v24

@izumisy/kyrage@1.5.3

Patch Changes

• #159 7026f08 Thanks @dependabot! - Bump c12 from 3.3.0 to 3.3.1

• #160 5779a2d Thanks @dependabot! - Bump ramda from 0.31.3 to 0.32.0

@izumisy/kyrage@1.5.2

Patch Changes

• #147 1d8161f Thanks @dependabot! - Bump zod from 4.1.11 to 4.1.12

• #150 e8b416f Thanks @dependabot! - Bump memfs from 4.48.1 to 4.49.0

• #151 d995dc0 Thanks @dependabot! - Bump mysql2 from 3.15.1 to 3.15.2

• #148 233c6e7 Thanks @dependabot! - Bump kysely from 0.28.7 to 0.28.8

• #149 e9b5a3e Thanks @dependabot! - Bump @types/node from 24.6.2 to 24.7.2

@izumisy/kyrage@1.5.1

Patch Changes

• #137 2922cb8 Thanks @IzumiSy! - Update dependencies

@izumisy/kyrage@1.5.0

Minor Changes

• #131 23e21eb Thanks @IzumiSy! - Add foreign key constraint merging to table creation operations with inline control option

  Kyrage now automatically merges foreign key constraints into CREATE TABLE statements alongside existing primary key and unique constraints. This reduces SQL operations and improves migration performance. Added inline option to schema builder's reference() method for fine-grained control over constraint merging.

  Example schema with inline foreign key:

  import { column as c, defineTable as t } from "@izumisy/kyrage";
  
  const users = t("users", {
    id: c("uuid", { primaryKey: true }),
  });
  
  const posts = t(
    "posts",
    {
      id: c("uuid", { primaryKey: true }),
      userId: c("uuid"),
    },
    (t) => [
      // Merged into CREATE TABLE (default: inline: true)
      t.reference("userId", users, "id"),
    ]
  );

  Example with separate constraint:

  const posts = t(
    "posts",
    {
      id: c("uuid", { primaryKey: true }),
      userId: c("uuid"),
    },
    (t) => [
      // Separate ALTER TABLE statement
      t.reference("userId", users, "id", { inline: false }),
    ]
  );

Patch Changes

• #131 23e21eb Thanks @IzumiSy! - Table operations are now sorted to always respect foreign key and other dependency relationships. Independent tables are ordered alphabetically, ensuring stable and predictable output for migrations and SQL generation.

  Example:

  import { column as c, defineTable as t } from "@izumisy/kyrage";
  
  const users = t("users", {
    id: c("uuid", { primaryKey: true }),
    name: c("varchar"),
  });
  
  const posts = t(
    "posts",
    {
      id: c("uuid", { primaryKey: true }),
      userId: c("uuid"),
      content: c("text"),
    },
    (t) => [
      t.reference("userId", users, "id"), // posts depends on users
    ]
  );
  
  const categories = t("categories", {
    id: c("uuid", { primaryKey: true }),
    label: c("varchar"),
  });

  The generated SQL will always be:

  CREATE TABLE categories (
    id uuid PRIMARY KEY,
    label varchar
  );
  
  CREATE TABLE users (
    id uuid PRIMARY KEY,
    name varchar
  );
  
  CREATE TABLE posts (
    id uuid PRIMARY KEY,
    userId uuid,
    content text,
    CONSTRAINT posts_userId_fkey FOREIGN KEY (userId) REFERENCES users(id)
  );

@izumisy/kyrage@1.4.0

Minor Changes

• #128 81034d5 Thanks @IzumiSy! - Optimize table creation by merging constraints into CREATE TABLE statements

  Kyrage now automatically combines table creation with primary key and unique constraints into a single CREATE TABLE statement, reducing the number of SQL operations and improving migration performance.

  Before:

  CREATE TABLE "users" ("id" integer, "email" varchar);
  ALTER TABLE "users" ADD CONSTRAINT "users_pkey" PRIMARY KEY ("id");
  ALTER TABLE "users" ADD CONSTRAINT "users_email_unique" UNIQUE ("email");

  After:

  CREATE TABLE "users" (
    "id" integer,
    "email" varchar,
    CONSTRAINT "users_pkey" PRIMARY KEY ("id"),
    CONSTRAINT "users_email_unique" UNIQUE ("email")
  );

  This optimization happens automatically when generating migrations - no changes to your schema definitions are required.

@izumisy/kyrage@1.3.1

Patch Changes

• #119 55b769a Thanks @IzumiSy! - Fix CockroachDB dialect to filter out system-generated rowid column during introspection

  CockroachDB automatically generates a rowid column for tables without an explicit primary key. This system-generated column was being included in introspection results, causing unwanted diffs between the actual database schema and user-defined configuration. The CockroachDB dialect now filters out the rowid column to match user expectations and prevent false positives in schema comparisons.

• #121 5fcfb5b Thanks @IzumiSy! - Fix container detection for dev database commands by properly matching multiple Docker labels. This resolves the issue where users would see "No running dev containers found" even when containers were actually running.

  The kyrage dev status, kyrage dev clean, and kyrage dev get-url commands were unable to detect running containers due to incomplete label matching in the container detection logic.

• #116 75fca73 Thanks @IzumiSy! - Fix migration provider to use the acquired DB connection by Kysely migrator

  Resolves issue where migration provider was not using the acquired DB connection passed to the Migration interface's up method, which is required for databases with connection limits like SQLite.