Skip to content

Drop the Sqlite3Shell CLI driver — SDK-only package#2

Merged
odrobnik merged 2 commits into
mainfrom
claude/sqlitekit-sdk-only
Jun 9, 2026
Merged

Drop the Sqlite3Shell CLI driver — SDK-only package#2
odrobnik merged 2 commits into
mainfrom
claude/sqlitekit-sdk-only

Conversation

@odrobnik

@odrobnik odrobnik commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Makes SQLiteKit purely the SQLite C library + idiomatic Swift glue (the SDK). The sqlite3 shell port (Parser + Sqlite3Executable + its tests) moves to SwiftPorts, where the rest of the sqlite3 CLI layer already lives.

Changes

  • Remove the Sqlite3Shell target, its .library product, and Sqlite3ShellTests.
  • Drop the ShellKit dependency — only the shell driver used it; the SDK never did.

Verification

swift build + swift test green (SDK-only; 46 tests).

⚠️ Breaking + landing order

Removing the Sqlite3Shell product is breaking for anything pinned to SQLiteKit main that uses it — currently SwiftBash (which is being repointed to SwiftPorts' shell port in its own PR). Part of a coordinated 4-repo change:

  1. ShellCommandKit: vend bridged Commands as instances + redact Sandbox.Denial ShellKit#16 (base — merge first)
  2. this PR + SwiftPorts (together — SwiftPorts needs SQLiteKit to be SDK-only, or its restored Sqlite3Shell target name collides with this one)
  3. SwiftBash last (its update stops depending on SQLiteKit's Sqlite3Shell; there's a brief window where SwiftBash main is red between this merge and SwiftBash's)

SDK-only consumers that depend only on the SQLiteKit product are unaffected.

🤖 Generated with Claude Code

The `sqlite3` shell port (`Parser` + `Sqlite3Executable` + its tests) moves
to SwiftPorts, where the rest of the CLI layer (the ArgumentParser wrapper +
the `sqlite3` executable) already lives. SQLiteKit is now purely the SQLite
C library plus its idiomatic Swift glue (the SDK) — one clean responsibility.

Removes the `Sqlite3Shell` target + `.library` product + `Sqlite3ShellTests`,
and the ShellKit dependency (only the driver used it; the SDK never did). SDK
consumers that only depended on the `SQLiteKit` product are unaffected.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

… scheme

iOS coverage is sufficient for the Apple-embedded story, so remove the
`build-tvos` and `build-visionos` jobs. Also drop the stale
`xcodebuild -scheme Sqlite3Shell` step from `build-ios` — that scheme no
longer exists (the shell port moved to SwiftPorts), which is what was
failing the iOS job. The kept Apple jobs (macOS / iOS / watchOS) build the
SDK against each device SDK; the full suites run on macOS / Linux / Windows
/ Android.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@odrobnik odrobnik merged commit f055755 into main Jun 9, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant