Rename crate to sqlrite-engine on crates.io#17
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The v0.1.1 canary release failed at
cargo publishwith a 403:The
sqlritename on crates.io was already taken by an unrelated project (RAG-oriented SQLite wrapper).sqlrite-engineis available, so this PR renames the published package and paves the way for a v0.1.2 canary retry.What changes
Cargo.toml:[package] name = "sqlrite-engine". The[lib] name = "sqlrite"and[[bin]] name = "sqlrite"are unchanged — downstream code still writesuse sqlrite::…and the REPL is stillsqlrite.package =key so the import alias stayssqlrite:sqlrite-ffi,sdk/python,sdk/nodejs,sdk/wasm,desktop/src-tauri.release.yml:cargo publish -p sqlrite-engine, updated crates.io URL + TOML snippet in the per-release body, plus umbrella release body's crates.io link.release-plan.md,roadmap.md,embedding.mdupdated with the new crate name + the reason for the rename.What doesn't change
sqlrite-vX.Y.Z) — they reference the product, not the crate name..rsfiles touched.Tags from the failed v0.1.1 canary
sqlrite-v0.1.1,sqlrite-ffi-v0.1.1,v0.1.1already exist on main (the tag-all step ran before publish-crate failed). Per the never-reuse-a-tag policy, they stay; the retry canary bumps to v0.1.2.Test plan
cargo check --workspace --exclude sqlrite-python --exclude sqlrite-nodejs— cleancargo check -p sqlrite-python -p sqlrite-nodejs— cleancargo checkinsidesdk/wasm/— clean (unrelated unused-mut warnings pre-exist)cargo test -p sqlrite-engine --lib— 162 passedrelease-pr.ymlat0.1.2→ review Release PR → merge → approvereleaseenv → watchsqlrite-engine 0.1.1— wait, 0.1.2 — appear on crates.io🤖 Generated with Claude Code