rahulmahadik · rahulmahadik · Aug 8, 2026 · Aug 8, 2026
diff --git a/.changeset/core-as-peer-dependency.md b/.changeset/core-as-peer-dependency.md
diff --git a/.changeset/mongo-row-cap-and-grounding.md b/.changeset/mongo-row-cap-and-grounding.md
diff --git a/packages/core/CHANGELOG.md b/packages/core/CHANGELOG.md
@@ -1,5 +1,25 @@
 # @asksql/core
 
+## 0.6.1
+
+### Patch Changes
+
+- 3e7cb1b: Clamp the MongoDB row cap the way the SQL side already did. A `maxRows` that was fractional, zero or
+  negative was passed straight into `$limit`, which MongoDB rejects outright, so the query failed
+  rather than returning fewer rows; a value above the engine's ceiling was injected unclamped while
+  the surrounding warning text named the capped number. Both engines now resolve the cap through one
+  shared function, so the prompt, the injected limit and the warning always name the same figure.
+
+  Stop reporting a backticked placeholder as a name missing from your schema. Backticks wrap more than
+  identifiers, so `` `?` ``, a date, or `:param` were each reported as a table or column that does not
+  exist. Hyphenated names, which are legal inside backticks, are still checked.
+
+  React: copy controls on explanations, schema answers, the query plan and the result grid; the
+  model's output is shown as it streams; the thread only follows new content when you are already at
+  the bottom; a schema answer no longer renders a red error while it is still being written; truncated
+  cells carry their full value; and `maxRows` takes effect on the next question rather than when the
+  connection changes.
+
 ## 0.6.0
 
 ### Minor Changes

diff --git a/packages/core/package.json b/packages/core/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@asksql/core",
-  "version": "0.6.0",
+  "version": "0.6.1",
   "description": "AskSQL engine: schema catalog, AST SQL guard, prompt pipeline, LLM orchestration. Zero database drivers.",
   "type": "module",
   "main": "./dist/index.js",

diff --git a/packages/duckdb/CHANGELOG.md b/packages/duckdb/CHANGELOG.md
@@ -1,5 +1,19 @@
 # @asksql/duckdb
 
+## 0.3.0
+
+### Minor Changes
+
+- 3e7cb1b: Depend on `@asksql/core` as a peer rather than a regular dependency. As a regular dependency, a
+  consumer pinned to a different core minor got a second copy of core installed under the connector
+  instead of a resolution error. Structural types survive that; identity does not, so
+  `error instanceof AskSqlError` was false for every error the connector threw and consumer error
+  handling silently stopped matching. The peer range is `>=0.6.0`, so npm and pnpm install one shared
+  core and report a real conflict when the consumer's pin cannot satisfy it.
+
+  Yarn (classic and berry) and npm with `legacy-peer-deps` do not install peers, so on those
+  `@asksql/core` must now be installed explicitly alongside the package.
+
 ## 0.2.7
 
 ### Patch Changes

diff --git a/packages/duckdb/package.json b/packages/duckdb/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@asksql/duckdb",
-  "version": "0.2.7",
+  "version": "0.3.0",
   "description": "DuckDB connector for AskSQL. Local analytical processing of CSV/JSON/Parquet files; the zero-backend file-analytics path.",
   "type": "module",
   "main": "./dist/index.js",
@@ -36,7 +36,7 @@
     }
   },
   "devDependencies": {
-    "@asksql/core": "workspace:>=0.6.0",
+    "@asksql/core": "workspace:>=0.6.1",
     "@duckdb/duckdb-wasm": "^1.32.0",
     "@duckdb/node-api": "1.5.4-r.1"
   },

diff --git a/packages/mcp/CHANGELOG.md b/packages/mcp/CHANGELOG.md
@@ -1,5 +1,19 @@
 # @asksql/mcp
 
+## 0.2.0
+
+### Minor Changes
+
+- 3e7cb1b: Depend on `@asksql/core` as a peer rather than a regular dependency. As a regular dependency, a
+  consumer pinned to a different core minor got a second copy of core installed under the connector
+  instead of a resolution error. Structural types survive that; identity does not, so
+  `error instanceof AskSqlError` was false for every error the connector threw and consumer error
+  handling silently stopped matching. The peer range is `>=0.6.0`, so npm and pnpm install one shared
+  core and report a real conflict when the consumer's pin cannot satisfy it.
+
+  Yarn (classic and berry) and npm with `legacy-peer-deps` do not install peers, so on those
+  `@asksql/core` must now be installed explicitly alongside the package.
+
 ## 0.1.9
 
 ### Patch Changes

diff --git a/packages/mcp/package.json b/packages/mcp/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@asksql/mcp",
-  "version": "0.1.9",
+  "version": "0.2.0",
   "description": "Model Context Protocol server for AskSQL: exposes list-connections / schema / query / run as MCP tools so AI agents can safely query registered databases (read-only, guarded).",
   "type": "module",
   "main": "./dist/index.js",
@@ -28,7 +28,7 @@
     }
   },
   "devDependencies": {
-    "@asksql/core": "workspace:>=0.6.0",
+    "@asksql/core": "workspace:>=0.6.1",
     "@modelcontextprotocol/sdk": "^1.29.0"
   },
   "license": "Apache-2.0",

diff --git a/packages/mongodb/CHANGELOG.md b/packages/mongodb/CHANGELOG.md
@@ -1,5 +1,19 @@
 # @asksql/mongodb
 
+## 0.2.0
+
+### Minor Changes
+
+- 3e7cb1b: Depend on `@asksql/core` as a peer rather than a regular dependency. As a regular dependency, a
+  consumer pinned to a different core minor got a second copy of core installed under the connector
+  instead of a resolution error. Structural types survive that; identity does not, so
+  `error instanceof AskSqlError` was false for every error the connector threw and consumer error
+  handling silently stopped matching. The peer range is `>=0.6.0`, so npm and pnpm install one shared
+  core and report a real conflict when the consumer's pin cannot satisfy it.
+
+  Yarn (classic and berry) and npm with `legacy-peer-deps` do not install peers, so on those
+  `@asksql/core` must now be installed explicitly alongside the package.
+
 ## 0.1.5
 
 ### Patch Changes

diff --git a/packages/mongodb/package.json b/packages/mongodb/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@asksql/mongodb",
-  "version": "0.1.5",
+  "version": "0.2.0",
   "description": "MongoDB connector for AskSQL. Sampling-based schema inference across collections + guarded read-only aggregation pipelines.",
   "type": "module",
   "main": "./dist/index.js",
@@ -23,7 +23,7 @@
     "mongodb": ">=6.0"
   },
   "devDependencies": {
-    "@asksql/core": "workspace:>=0.6.0",
+    "@asksql/core": "workspace:>=0.6.1",
     "mongodb": "^6.10.0"
   },
   "license": "Apache-2.0",

diff --git a/packages/mysql/CHANGELOG.md b/packages/mysql/CHANGELOG.md
@@ -1,5 +1,19 @@
 # @asksql/mysql
 
+## 0.3.0
+
+### Minor Changes
+
+- 3e7cb1b: Depend on `@asksql/core` as a peer rather than a regular dependency. As a regular dependency, a
+  consumer pinned to a different core minor got a second copy of core installed under the connector
+  instead of a resolution error. Structural types survive that; identity does not, so
+  `error instanceof AskSqlError` was false for every error the connector threw and consumer error
+  handling silently stopped matching. The peer range is `>=0.6.0`, so npm and pnpm install one shared
+  core and report a real conflict when the consumer's pin cannot satisfy it.
+
+  Yarn (classic and berry) and npm with `legacy-peer-deps` do not install peers, so on those
+  `@asksql/core` must now be installed explicitly alongside the package.
+
 ## 0.2.6
 
 ### Patch Changes

diff --git a/packages/mysql/package.json b/packages/mysql/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@asksql/mysql",
-  "version": "0.2.6",
+  "version": "0.3.0",
   "description": "MySQL connector for AskSQL. information_schema introspection + read-only session enforcement.",
   "type": "module",
   "main": "./dist/index.js",
@@ -23,7 +23,7 @@
     "mysql2": ">=3.6"
   },
   "devDependencies": {
-    "@asksql/core": "workspace:>=0.6.0",
+    "@asksql/core": "workspace:>=0.6.1",
     "mysql2": "^3.22.6"
   },
   "license": "Apache-2.0",

diff --git a/packages/oracle/CHANGELOG.md b/packages/oracle/CHANGELOG.md
@@ -1,5 +1,19 @@
 # @asksql/oracle
 
+## 0.2.0
+
+### Minor Changes
+
+- 3e7cb1b: Depend on `@asksql/core` as a peer rather than a regular dependency. As a regular dependency, a
+  consumer pinned to a different core minor got a second copy of core installed under the connector
+  instead of a resolution error. Structural types survive that; identity does not, so
+  `error instanceof AskSqlError` was false for every error the connector threw and consumer error
+  handling silently stopped matching. The peer range is `>=0.6.0`, so npm and pnpm install one shared
+  core and report a real conflict when the consumer's pin cannot satisfy it.
+
+  Yarn (classic and berry) and npm with `legacy-peer-deps` do not install peers, so on those
+  `@asksql/core` must now be installed explicitly alongside the package.
+
 ## 0.1.4
 
 ### Patch Changes

diff --git a/packages/oracle/package.json b/packages/oracle/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@asksql/oracle",
-  "version": "0.1.4",
+  "version": "0.2.0",
   "description": "Oracle Database connector for AskSQL. Data-dictionary schema introspection (tables, views, columns, primary/foreign keys, comments) + read-only transaction enforcement. Uses the oracledb driver in pure-JS Thin mode (no Instant Client).",
   "type": "module",
   "main": "./dist/index.js",
@@ -23,7 +23,7 @@
     "oracledb": ">=6.0"
   },
   "devDependencies": {
-    "@asksql/core": "workspace:>=0.6.0",
+    "@asksql/core": "workspace:>=0.6.1",
     "oracledb": "^6.5.0"
   },
   "license": "Apache-2.0",

diff --git a/packages/postgres/CHANGELOG.md b/packages/postgres/CHANGELOG.md
@@ -1,5 +1,19 @@
 # @asksql/postgres
 
+## 0.3.0
+
+### Minor Changes
+
+- 3e7cb1b: Depend on `@asksql/core` as a peer rather than a regular dependency. As a regular dependency, a
+  consumer pinned to a different core minor got a second copy of core installed under the connector
+  instead of a resolution error. Structural types survive that; identity does not, so
+  `error instanceof AskSqlError` was false for every error the connector threw and consumer error
+  handling silently stopped matching. The peer range is `>=0.6.0`, so npm and pnpm install one shared
+  core and report a real conflict when the consumer's pin cannot satisfy it.
+
+  Yarn (classic and berry) and npm with `legacy-peer-deps` do not install peers, so on those
+  `@asksql/core` must now be installed explicitly alongside the package.
+
 ## 0.2.7
 
 ### Patch Changes

diff --git a/packages/postgres/package.json b/packages/postgres/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@asksql/postgres",
-  "version": "0.2.7",
+  "version": "0.3.0",
   "description": "PostgreSQL connector for AskSQL. Full schema introspection (tables, views, indexes, triggers, functions, enums, FKs) + read-only session enforcement.",
   "type": "module",
   "main": "./dist/index.js",
@@ -23,7 +23,7 @@
     "pg": ">=8.11"
   },
   "devDependencies": {
-    "@asksql/core": "workspace:>=0.6.0",
+    "@asksql/core": "workspace:>=0.6.1",
     "@types/pg": "^8.20.0",
     "pg": "^8.22.0"
   },

diff --git a/packages/react/CHANGELOG.md b/packages/react/CHANGELOG.md
@@ -1,5 +1,35 @@
 # @asksql/react
 
+## 0.3.0
+
+### Minor Changes
+
+- 3e7cb1b: Depend on `@asksql/core` as a peer rather than a regular dependency. As a regular dependency, a
+  consumer pinned to a different core minor got a second copy of core installed under the connector
+  instead of a resolution error. Structural types survive that; identity does not, so
+  `error instanceof AskSqlError` was false for every error the connector threw and consumer error
+  handling silently stopped matching. The peer range is `>=0.6.0`, so npm and pnpm install one shared
+  core and report a real conflict when the consumer's pin cannot satisfy it.
+
+  Yarn (classic and berry) and npm with `legacy-peer-deps` do not install peers, so on those
+  `@asksql/core` must now be installed explicitly alongside the package.
+
+- 3e7cb1b: Clamp the MongoDB row cap the way the SQL side already did. A `maxRows` that was fractional, zero or
+  negative was passed straight into `$limit`, which MongoDB rejects outright, so the query failed
+  rather than returning fewer rows; a value above the engine's ceiling was injected unclamped while
+  the surrounding warning text named the capped number. Both engines now resolve the cap through one
+  shared function, so the prompt, the injected limit and the warning always name the same figure.
+
+  Stop reporting a backticked placeholder as a name missing from your schema. Backticks wrap more than
+  identifiers, so `` `?` ``, a date, or `:param` were each reported as a table or column that does not
+  exist. Hyphenated names, which are legal inside backticks, are still checked.
+
+  React: copy controls on explanations, schema answers, the query plan and the result grid; the
+  model's output is shown as it streams; the thread only follows new content when you are already at
+  the bottom; a schema answer no longer renders a red error while it is still being written; truncated
+  cells carry their full value; and `maxRows` takes effect on the next question rather than when the
+  connection changes.
+
 ## 0.2.3
 
 ### Patch Changes

diff --git a/packages/react/package.json b/packages/react/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@asksql/react",
-  "version": "0.2.3",
+  "version": "0.3.0",
   "description": "React UI for AskSQL: <AskSqlChat/> full-page chat and <AskSqlBubble/> floating chat-head, plus headless hooks. Light/dark, loading/empty/error states built in.",
   "type": "module",
   "main": "./dist/index.js",
@@ -24,7 +24,7 @@
     "react-dom": ">=18"
   },
   "devDependencies": {
-    "@asksql/core": "workspace:>=0.6.0",
+    "@asksql/core": "workspace:>=0.6.1",
     "@types/react": "^19.2.17",
     "@types/react-dom": "^19.2.3",
     "react": "^19.2.7",

diff --git a/packages/server/CHANGELOG.md b/packages/server/CHANGELOG.md
@@ -1,5 +1,19 @@
 # @asksql/server
 
+## 0.6.0
+
+### Minor Changes
+
+- 3e7cb1b: Depend on `@asksql/core` as a peer rather than a regular dependency. As a regular dependency, a
+  consumer pinned to a different core minor got a second copy of core installed under the connector
+  instead of a resolution error. Structural types survive that; identity does not, so
+  `error instanceof AskSqlError` was false for every error the connector threw and consumer error
+  handling silently stopped matching. The peer range is `>=0.6.0`, so npm and pnpm install one shared
+  core and report a real conflict when the consumer's pin cannot satisfy it.
+
+  Yarn (classic and berry) and npm with `legacy-peer-deps` do not install peers, so on those
+  `@asksql/core` must now be installed explicitly alongside the package.
+
 ## 0.5.1
 
 ### Patch Changes