docs(release): bump displayed version to 0.12.0 (site + install snippets)#160
Merged
Conversation
…ets) v0.12.0 is published across crates.io / npm / PyPI / WASM / Go, so update the version surfaces that the release pipeline doesn't touch: - web/src/lib/site.ts: SITE.version 0.11.0 → 0.12.0 — the single source of truth the marketing site reads (hero badge, docs header, SDK showcase cards, structured-data softwareVersion). - README.md / docs/embedding.md / docs/ask.md: the Rust install snippets pinned `sqlrite-engine = "0.11"` / `sqlrite-ask = "0.11"`. Bump to "0.12" so the documented pin installs the current release. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
joaoh82
added a commit
that referenced
this pull request
Jun 10, 2026
…ets) (#163) * docs(release): bump displayed version to 0.13.0 (site + install snippets) Same shape as #160 for v0.12.0: the Cargo install snippets in README, docs/ask.md, and docs/embedding.md, plus the site-wide version constant in web/src/lib/site.ts. v0.13.0 shipped HAVING (SQLR-52, #161). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * chore(playground): refresh vendored WASM bundle to the 0.13.0 engine The /playground pkg is a pinned copy Vercel never rebuilds, so it was still serving the pre-0.12 engine (last refreshed in SQLR-42). Rebuilt via the documented flow in examples/wasm-playground/README.md; only the .wasm binary changed (no SDK API change, glue files identical). Also picks up sdk/wasm/Cargo.lock's 0.13.0 bump — sdk/wasm sits outside the workspace, so the Release PR's lock refresh couldn't reach it. Smoke-verified in Node: GROUP BY ... HAVING total > 100 returns the filtered group through the new bundle. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <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.
Summary
Follow-up to the v0.12.0 release (#159). The release pipeline bumps the package manifests but not the displayed version surfaces, so this brings those in line (same set of files as the 0.11.0 precedent, #155):
web/src/lib/site.ts—SITE.version0.11.0 → 0.12.0. Single source of truth the marketing site reads: hero badge, docs page header, SDK showcase cards, and thesoftwareVersionin structured data (web/src/app/page.tsxderives it fromSITE.version).README.md/docs/embedding.md/docs/ask.md— Rust install snippetssqlrite-engine = "0.11"/sqlrite-ask = "0.11"→"0.12", so a copy-paste resolves the current release.Left untouched intentionally:
env_logger 0.11/thiserror/sqlparserdep references, and historical0.1xmentions inrelease-plan.md/release-secrets.md/design-decisions.md/phase-8-plan.md(those describe past waves, not the current version).🤖 Generated with Claude Code