From d390120e2f659a8e1f29e75ee14d77c1b74a9134 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Fri, 28 Aug 2026 05:12:39 +0000
Subject: [PATCH] chore: release package

---
 .changeset/bun-sqlite-dialect.md | 25 -------------------------
 CHANGELOG.md                     | 27 +++++++++++++++++++++++++++
 package.json                     |  2 +-
 3 files changed, 28 insertions(+), 26 deletions(-)
 delete mode 100644 .changeset/bun-sqlite-dialect.md

diff --git a/.changeset/bun-sqlite-dialect.md b/.changeset/bun-sqlite-dialect.md
deleted file mode 100644
index 6caeaae..0000000
--- a/.changeset/bun-sqlite-dialect.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-"kysely-bun-sqlite-dialect": minor
----
-
-Add `BunSqliteDialect`, a Kysely dialect for Bun's native `bun:sqlite` driver.
-
-Kysely's built-in `SqliteDialect` targets `better-sqlite3` and silently returns
-no rows on `bun:sqlite`, because it branches on `Statement.reader`, which Bun
-does not have. This dialect uses `Statement.columnNames` instead and drives the
-rest of the `bun:sqlite` API natively: prepared-statement caching via
-`db.query()`, private cursors for `.stream()`, savepoints, and `deferred` /
-`immediate` / `exclusive` transaction behavior.
-
-Documents that Bun ships SQLite with `DQS=3`, so an unresolvable double-quoted
-identifier is accepted as a string literal rather than raising `no such column`
-as it does under better-sqlite3.
-
-Requires Kysely `>=0.29.0`. Kysely 0.28 is not supported: its connection mutex
-lived inside `SqliteDriver` rather than `RuntimeDriver`, so a dialect written
-against 0.29 has no lock of its own and parallel transactions interleave on
-0.28's single connection.
-
-Declares `engines.bun` only, with no `engines.node`: the published JavaScript
-never imports `bun:sqlite` itself, so a Node floor would only make npm and pnpm
-warn or fail for consumers over a build-time concern.
diff --git a/CHANGELOG.md b/CHANGELOG.md
index e69de29..79573f1 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -0,0 +1,27 @@
+# kysely-bun-sqlite-dialect
+
+## 0.1.0
+
+### Minor Changes
+
+- [`17b69e8`](https://github.com/disaresta-org/kysely-bun-sqlite-dialect/commit/17b69e812445e858c7679154bbc48783352bf5e5) Thanks [@theogravity](https://github.com/theogravity)! - Add `BunSqliteDialect`, a Kysely dialect for Bun's native `bun:sqlite` driver.
+  
+  Kysely's built-in `SqliteDialect` targets `better-sqlite3` and silently returns
+  no rows on `bun:sqlite`, because it branches on `Statement.reader`, which Bun
+  does not have. This dialect uses `Statement.columnNames` instead and drives the
+  rest of the `bun:sqlite` API natively: prepared-statement caching via
+  `db.query()`, private cursors for `.stream()`, savepoints, and `deferred` /
+  `immediate` / `exclusive` transaction behavior.
+  
+  Documents that Bun ships SQLite with `DQS=3`, so an unresolvable double-quoted
+  identifier is accepted as a string literal rather than raising `no such column`
+  as it does under better-sqlite3.
+  
+  Requires Kysely `>=0.29.0`. Kysely 0.28 is not supported: its connection mutex
+  lived inside `SqliteDriver` rather than `RuntimeDriver`, so a dialect written
+  against 0.29 has no lock of its own and parallel transactions interleave on
+  0.28's single connection.
+  
+  Declares `engines.bun` only, with no `engines.node`: the published JavaScript
+  never imports `bun:sqlite` itself, so a Node floor would only make npm and pnpm
+  warn or fail for consumers over a build-time concern.
diff --git a/package.json b/package.json
index ff9ee09..4f7ed9a 100644
--- a/package.json
+++ b/package.json
@@ -1,7 +1,7 @@
 {
   "name": "kysely-bun-sqlite-dialect",
   "description": "Kysely dialect for Bun's native bun:sqlite driver",
-  "version": "0.0.0",
+  "version": "0.1.0",
   "type": "module",
   "main": "./dist/index.cjs",
   "module": "./dist/index.js",