diff --git a/.changeset/core-as-peer-dependency.md b/.changeset/core-as-peer-dependency.md deleted file mode 100644 index d37ce6e..0000000 --- a/.changeset/core-as-peer-dependency.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -'@asksql/duckdb': minor -'@asksql/mcp': minor -'@asksql/mongodb': minor -'@asksql/mysql': minor -'@asksql/oracle': minor -'@asksql/postgres': minor -'@asksql/react': minor -'@asksql/server': minor -'@asksql/sqlite': minor ---- - -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. diff --git a/.changeset/mongo-row-cap-and-grounding.md b/.changeset/mongo-row-cap-and-grounding.md deleted file mode 100644 index 6496564..0000000 --- a/.changeset/mongo-row-cap-and-grounding.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -'@asksql/core': patch -'@asksql/react': minor ---- - -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. diff --git a/packages/core/CHANGELOG.md b/packages/core/CHANGELOG.md index a86d05e..1a0a03a 100644 --- 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 index 327f9dd..364dff3 100644 --- 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 index 03f3859..e5ef65d 100644 --- 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 index a96ad51..0f04f6b 100644 --- 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 index 92f0062..3c3b9c4 100644 --- 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 index 2223e18..4afd693 100644 --- 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 index ed4cbb2..8cc2e3b 100644 --- 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 index 4e2a108..49028dc 100644 --- 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 index 93daefc..8cef46d 100644 --- 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 index a6903a1..c6832aa 100644 --- 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 index 75ac92c..833b806 100644 --- 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 index 107a4a6..7809ad8 100644 --- 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 index 60d63f8..93e7af8 100644 --- 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 index e9f9e1e..2e38c6b 100644 --- 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 index af96ab2..aea5ddd 100644 --- 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 index b9d7e99..ec5b053 100644 --- 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: full-page chat and 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 index 404cec7..8b7322d 100644 --- 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 diff --git a/packages/server/package.json b/packages/server/package.json index b8d752c..86a0ba5 100644 --- a/packages/server/package.json +++ b/packages/server/package.json @@ -1,6 +1,6 @@ { "name": "@asksql/server", - "version": "0.5.1", + "version": "0.6.0", "description": "AskSQL server sidecar: credential-holding HTTP handler with auth hook, server-side SQL guard, audit log. Framework-agnostic + Express/Next adapters.", "type": "module", "main": "./dist/index.js", @@ -62,13 +62,13 @@ "text2sql" ], "devDependencies": { - "@asksql/core": "workspace:>=0.6.0", - "@asksql/postgres": "workspace:>=0.2.7", - "@asksql/mysql": "workspace:>=0.2.6", - "@asksql/oracle": "workspace:>=0.1.4", - "@asksql/mongodb": "workspace:>=0.1.5", - "@asksql/sqlite": "workspace:>=0.3.2", - "@asksql/duckdb": "workspace:>=0.2.7" + "@asksql/core": "workspace:>=0.6.1", + "@asksql/postgres": "workspace:>=0.3.0", + "@asksql/mysql": "workspace:>=0.3.0", + "@asksql/oracle": "workspace:>=0.2.0", + "@asksql/mongodb": "workspace:>=0.2.0", + "@asksql/sqlite": "workspace:>=0.4.0", + "@asksql/duckdb": "workspace:>=0.3.0" }, "peerDependencies": { "@asksql/core": "workspace:>=0.6.0", diff --git a/packages/sqlite/CHANGELOG.md b/packages/sqlite/CHANGELOG.md index c4d2f01..6bdbfb0 100644 --- a/packages/sqlite/CHANGELOG.md +++ b/packages/sqlite/CHANGELOG.md @@ -1,5 +1,19 @@ # @asksql/sqlite +## 0.4.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.3.2 ### Patch Changes diff --git a/packages/sqlite/package.json b/packages/sqlite/package.json index a6ff48c..1f1bdfd 100644 --- a/packages/sqlite/package.json +++ b/packages/sqlite/package.json @@ -1,6 +1,6 @@ { "name": "@asksql/sqlite", - "version": "0.3.2", + "version": "0.4.0", "description": "SQLite connector for AskSQL. Works with better-sqlite3 or the built-in node:sqlite; full PRAGMA-based introspection.", "type": "module", "main": "./dist/index.js", @@ -28,7 +28,7 @@ } }, "devDependencies": { - "@asksql/core": "workspace:>=0.6.0" + "@asksql/core": "workspace:>=0.6.1" }, "license": "Apache-2.0", "engines": { diff --git a/packages/widget/CHANGELOG.md b/packages/widget/CHANGELOG.md index 318b614..711e6ba 100644 --- a/packages/widget/CHANGELOG.md +++ b/packages/widget/CHANGELOG.md @@ -1,5 +1,13 @@ # @asksql/widget +## 0.2.6 + +### Patch Changes + +- Updated dependencies [3e7cb1b] +- Updated dependencies [3e7cb1b] + - @asksql/react@0.3.0 + ## 0.2.5 ### Patch Changes diff --git a/packages/widget/package.json b/packages/widget/package.json index 0093c3d..19c3410 100644 --- a/packages/widget/package.json +++ b/packages/widget/package.json @@ -1,6 +1,6 @@ { "name": "@asksql/widget", - "version": "0.2.5", + "version": "0.2.6", "description": "Vanilla-JS AskSQL embed for non-React pages. Mounts the bubble/chat into a shadow root so host CSS never bleeds in or out.", "type": "module", "main": "./dist/index.js", diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml index 390d126..26d0611 100644 --- a/pnpm-lock.yaml +++ b/pnpm-lock.yaml @@ -313,7 +313,7 @@ importers: packages/duckdb: devDependencies: '@asksql/core': - specifier: workspace:>=0.6.0 + specifier: workspace:>=0.6.1 version: link:../core '@duckdb/duckdb-wasm': specifier: ^1.32.0 @@ -325,7 +325,7 @@ importers: packages/mcp: devDependencies: '@asksql/core': - specifier: workspace:>=0.6.0 + specifier: workspace:>=0.6.1 version: link:../core '@modelcontextprotocol/sdk': specifier: ^1.29.0 @@ -334,7 +334,7 @@ importers: packages/mongodb: devDependencies: '@asksql/core': - specifier: workspace:>=0.6.0 + specifier: workspace:>=0.6.1 version: link:../core mongodb: specifier: ^6.10.0 @@ -343,7 +343,7 @@ importers: packages/mysql: devDependencies: '@asksql/core': - specifier: workspace:>=0.6.0 + specifier: workspace:>=0.6.1 version: link:../core mysql2: specifier: ^3.22.6 @@ -352,7 +352,7 @@ importers: packages/oracle: devDependencies: '@asksql/core': - specifier: workspace:>=0.6.0 + specifier: workspace:>=0.6.1 version: link:../core oracledb: specifier: ^6.5.0 @@ -361,7 +361,7 @@ importers: packages/postgres: devDependencies: '@asksql/core': - specifier: workspace:>=0.6.0 + specifier: workspace:>=0.6.1 version: link:../core '@types/pg': specifier: ^8.20.0 @@ -373,7 +373,7 @@ importers: packages/react: devDependencies: '@asksql/core': - specifier: workspace:>=0.6.0 + specifier: workspace:>=0.6.1 version: link:../core '@types/react': specifier: ^19.2.17 @@ -395,25 +395,25 @@ importers: version: 3.0.9(zod@4.4.3) devDependencies: '@asksql/core': - specifier: workspace:>=0.6.0 + specifier: workspace:>=0.6.1 version: link:../core '@asksql/duckdb': - specifier: workspace:>=0.2.7 + specifier: workspace:>=0.3.0 version: link:../duckdb '@asksql/mongodb': - specifier: workspace:>=0.1.5 + specifier: workspace:>=0.2.0 version: link:../mongodb '@asksql/mysql': - specifier: workspace:>=0.2.6 + specifier: workspace:>=0.3.0 version: link:../mysql '@asksql/oracle': - specifier: workspace:>=0.1.4 + specifier: workspace:>=0.2.0 version: link:../oracle '@asksql/postgres': - specifier: workspace:>=0.2.7 + specifier: workspace:>=0.3.0 version: link:../postgres '@asksql/sqlite': - specifier: workspace:>=0.3.2 + specifier: workspace:>=0.4.0 version: link:../sqlite packages/sqlite: @@ -423,7 +423,7 @@ importers: version: 12.11.1 devDependencies: '@asksql/core': - specifier: workspace:>=0.6.0 + specifier: workspace:>=0.6.1 version: link:../core packages/vscode: