Rename crate to sqlrite-engine on crates.io (lib name unchanged) (#17)

The `sqlrite` crate name on crates.io was already taken by an
unrelated project (RAG-oriented SQLite wrapper), which made the
v0.1.1 canary's `cargo publish` step fail with a 403. Rename the
published package to `sqlrite-engine`, keep the [lib] name and
[[bin]] name as `sqlrite` so downstream Rust code continues to
write `use sqlrite::…` with no change.

Workspace members depend on the engine via:

    sqlrite = { package = "sqlrite-engine", path = "…" }

which keeps the import alias stable across the FFI shim, the
Python / Node.js / WASM SDKs, and the Tauri desktop app.

Also updates release.yml — `cargo publish -p sqlrite-engine`, the
per-release body's crates.io URL + TOML snippet, and the umbrella
release body's crates.io link — plus docs (release-plan, roadmap,
embedding) to match.

Per the never-reuse-a-tag policy, tags sqlrite-v0.1.1 /
sqlrite-ffi-v0.1.1 / v0.1.1 (created during the failed canary)
stay on main; the retry canary cuts v0.1.2.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: joaoh82

.github/workflows/release.yml

@@ -152,24 +152,31 @@ jobs:
         run: |
           # `--no-verify` skips the rebuild+test that publish does
           # by default — CI already ran on the same commit on the
-          # Release PR, so re-running here is duplicate work. Also
-          # `-p sqlrite` is explicit about which workspace member
-          # we're publishing (could be omitted since sqlrite is the
-          # root package, but being explicit protects against
-          # future layout changes).
-          cargo publish -p sqlrite --no-verify
+          # Release PR, so re-running here is duplicate work.
+          #
+          # Package name on crates.io is `sqlrite-engine`, not
+          # `sqlrite` — the latter was taken by an unrelated project
+          # (see root Cargo.toml for context). The [lib] name is
+          # still `sqlrite`, so downstream code writes `use sqlrite::…`.
+          cargo publish -p sqlrite-engine --no-verify
 
       - name: GitHub Release
         uses: softprops/action-gh-release@v2
         with:
           tag_name: sqlrite-v${{ needs.detect.outputs.version }}
           name: Rust engine v${{ needs.detect.outputs.version }}
           body: |
-            Published to crates.io: https://crates.io/crates/sqlrite/${{ needs.detect.outputs.version }}
+            Published to crates.io: https://crates.io/crates/sqlrite-engine/${{ needs.detect.outputs.version }}
 
             ```toml
             [dependencies]
-            sqlrite = "${{ needs.detect.outputs.version }}"
+            sqlrite-engine = "${{ needs.detect.outputs.version }}"
+            ```
+
+            ```rust
+            // The [lib] name stays `sqlrite`, so the import alias is
+            // the short one even though the package name is longer.
+            use sqlrite::{Database, ExecutionResult};
             ```
 
             See the umbrella release [v${{ needs.detect.outputs.version }}](../../releases/tag/v${{ needs.detect.outputs.version }}) for the full changelog.
@@ -295,7 +302,7 @@ jobs:
 
             Per-product releases in this wave:
 
-            - 🦀 [Rust engine](../../releases/tag/sqlrite-v${{ needs.detect.outputs.version }}) → [crates.io](https://crates.io/crates/sqlrite/${{ needs.detect.outputs.version }})
+            - 🦀 [Rust engine](../../releases/tag/sqlrite-v${{ needs.detect.outputs.version }}) → [crates.io](https://crates.io/crates/sqlrite-engine/${{ needs.detect.outputs.version }})
             - 🔧 [C FFI](../../releases/tag/sqlrite-ffi-v${{ needs.detect.outputs.version }}) — prebuilt `libsqlrite_c` for Linux x86_64/aarch64, macOS aarch64, Windows x86_64
 
             _Python / Node.js / WASM / Go / desktop SDKs land as their publish jobs come online (Phases 6e–6i)._

Cargo.lock

@@ -13,12 +13,25 @@ members = [".", "desktop/src-tauri", "sqlrite-ffi", "sdk/python", "sdk/nodejs"]
 resolver = "3"
 
 [package]
-name = "sqlrite"
+# Published to crates.io as `sqlrite-engine` because `sqlrite` was
+# already taken (unrelated project — RAG-oriented SQLite wrapper). The
+# lib target below keeps `name = "sqlrite"`, so downstream Rust code
+# still writes `use sqlrite::…` — only the `cargo add` line and the
+# dependency declaration change:
+#
+#     [dependencies]
+#     sqlrite-engine = "0.1"
+#     # then in code: use sqlrite::{Database, …};
+#
+# Any workspace member here that depends on the engine uses the
+# `package =` key so the import name stays `sqlrite` internally:
+#     sqlrite = { package = "sqlrite-engine", path = "…" }
+name = "sqlrite-engine"
 version = "0.1.1"
 authors = ["Joao Henrique Machado Silva <joaoh82@gmail.com>"]
 edition = "2024"
 rust-version = "1.85"
-description = "Light version of SQLite developed with Rust"
+description = "Light version of SQLite developed with Rust. Published as `sqlrite-engine` on crates.io; import as `use sqlrite::…`."
 repository = "https://github.com/joaoh82/rust_sqlite"
 license = "MIT"
 

Cargo.toml

@@ -21,7 +21,9 @@ tauri-build = { version = "2", features = [] }
 [dependencies]
 # Engine lives at the workspace root; reference it by path. Version
 # pinning can wait for a proper release cut.
-sqlrite = { path = "../.." }
+# `package = "sqlrite-engine"` — crates.io name — with an import alias
+# of `sqlrite` so Tauri command code can keep saying `use sqlrite::…`.
+sqlrite = { package = "sqlrite-engine", path = "../.." }
 
 tauri = { version = "2", features = [] }
 # Tauri 2 plugins must be opted into explicitly; the dialog plugin

desktop/src-tauri/Cargo.toml

@@ -215,7 +215,7 @@ A fix in the Rust engine propagates through one wrapper update per language rath
 
 Phase 6 lands GitHub Actions CI + release automation:
 
-- **crates.io** — `sqlrite` crate
+- **crates.io** — `sqlrite-engine` crate (published under a different name from the `sqlrite` lib target because the short name was already taken; users `cargo add sqlrite-engine` but still write `use sqlrite::…`)
 - **PyPI** — `sqlrite` wheels (manylinux x86_64/aarch64, macOS universal, Windows x86_64)
 - **npm** — `sqlrite` (Node) + `sqlrite-wasm` (browser) packages
 - **Go modules** — `sdk/go/v*` git tags

docs/embedding.md

@@ -208,8 +208,12 @@ The "publish" half. Auto-fires on the release commit.
     them. Runs *before* the publish jobs — if a tag already exists
     (accidental re-run, cosmic ray), the whole workflow aborts
     cleanly.
-  - **publish-crate** — `cargo publish` the root crate to crates.io.
-    Creates GitHub Release `sqlrite-vX.Y.Z`.
+  - **publish-crate** — `cargo publish -p sqlrite-engine` the root
+    crate to crates.io. (The crates.io name is `sqlrite-engine`, not
+    `sqlrite`, because the short name was already taken by an
+    unrelated project; the `[lib] name = "sqlrite"` keeps `use
+    sqlrite::…` valid at import sites.) Creates GitHub Release
+    `sqlrite-vX.Y.Z`.
   - **publish-ffi** — matrix build of `libsqlrite_c` for
     `{linux-x86_64, linux-aarch64, macos-universal, windows-x86_64}`.
     Packages each as a tarball containing the `.so`/`.dylib`/`.dll`,

docs/release-plan.md

@@ -387,13 +387,15 @@ Jobs wired up in Phase 6d:
 
 1. **detect** — parse version from commit message or dispatch input. Outputs `version` + `should_release`.
 2. **tag-all** — idempotent: creates `sqlrite-vX.Y.Z`, `sqlrite-ffi-vX.Y.Z`, and umbrella `vX.Y.Z`; skips any tag that already exists so "Re-run failed jobs" works cleanly after a partial-failure scenario.
-3. **publish-crate** — `cargo publish -p sqlrite --no-verify` using `CRATES_IO_TOKEN` from the `release` environment (required-reviewer gate applies). Creates the per-product GitHub Release `sqlrite-vX.Y.Z`.
+3. **publish-crate** — `cargo publish -p sqlrite-engine --no-verify` using `CRATES_IO_TOKEN` from the `release` environment (required-reviewer gate applies). Creates the per-product GitHub Release `sqlrite-vX.Y.Z`. The crates.io name is `sqlrite-engine` because the short `sqlrite` name was taken by an unrelated project; the `[lib] name = "sqlrite"` preserves `use sqlrite::…` at the import site.
 4. **publish-ffi** — matrix build of `libsqlrite_c` on Linux x86_64 (`ubuntu-latest`), Linux aarch64 (`ubuntu-24.04-arm`), macOS aarch64 (`macos-latest`), Windows x86_64 (`windows-latest`). Packages the cdylib + staticlib + `sqlrite.h` + README stub into a tarball, uploads to the `sqlrite-ffi-vX.Y.Z` GitHub Release. macOS universal (x86_64 + aarch64 lipo'd together) is a follow-up — MVP ships aarch64-only for Mac; add `macos-13` to the matrix if x86 demand materializes.
 5. **finalize** — creates the umbrella `vX.Y.Z` GitHub Release with GitHub's native auto-generated notes (`generate_release_notes: true`). Body links to every per-product release from this wave.
 
 Products whose publish jobs land in later phases (desktop, Python, Node.js, WASM, Go) aren't tagged yet — `tag-all` only creates tags for products that have an active publish job. Cleaner than creating empty releases for products we can't actually ship.
 
-**Verification path**: push this branch → merge → dispatch `release-pr.yml` with version `0.1.1` → review the auto-opened PR → merge → approve the `release` environment prompt → watch crates.io show `sqlrite 0.1.1` + Release page show two per-product releases + umbrella release. Once that works end-to-end, 6e lands the desktop publish, and we bump to `v0.1.2` for the next canary.
+**Verification path**: push this branch → merge → dispatch `release-pr.yml` with version `0.1.1` → review the auto-opened PR → merge → approve the `release` environment prompt → watch crates.io show `sqlrite-engine 0.1.1` + Release page show two per-product releases + umbrella release. Once that works end-to-end, 6e lands the desktop publish, and we bump to `v0.1.2` for the next canary.
+
+> **v0.1.1 canary retrospective** *(2026-04-22)* — first publish attempt failed on `cargo publish` with a 403 because the `sqlrite` crate name on crates.io is owned by an unrelated RAG-SQLite project. Renamed the package to `sqlrite-engine` (lib / bin names unchanged, so `use sqlrite::…` still works for consumers). Tags `sqlrite-v0.1.1` / `sqlrite-ffi-v0.1.1` / `v0.1.1` stay on main per the never-reuse-a-tag policy; the next canary cuts `v0.1.2` under the new crate name.
 
 ### Phase 6e — Desktop publish
 

docs/roadmap.md

@@ -22,7 +22,11 @@ crate-type = ["cdylib", "rlib"]
 path = "src/lib.rs"
 
 [dependencies]
-sqlrite = { path = "../.." }
+# `package = "sqlrite-engine"` — crates.io name — with an import alias
+# of `sqlrite` so src/ code can keep saying `use sqlrite::…`. See root
+# Cargo.toml for the full story on why the package name differs from
+# the lib name.
+sqlrite = { package = "sqlrite-engine", path = "../.." }
 
 # napi-rs 2.x — mature + widely deployed (used by prisma, swc,
 # lightningcss, etc.). Version 2.16 adds `serde-json` features we

sdk/nodejs/Cargo.toml

@@ -23,7 +23,11 @@ crate-type = ["cdylib", "rlib"]
 path = "src/lib.rs"
 
 [dependencies]
-sqlrite = { path = "../.." }
+# `package = "sqlrite-engine"` — crates.io name — with an import alias
+# of `sqlrite` so src/ code can keep saying `use sqlrite::…`. See root
+# Cargo.toml for the full story on why the package name differs from
+# the lib name.
+sqlrite = { package = "sqlrite-engine", path = "../.." }
 
 # PyO3 with the `abi3-py38` feature so one wheel works on every
 # CPython 3.8+ release — no per-Python-version rebuild.