feat(web): v0.10.0 launch — concurrent-writes blog post + site update (SQLR-57)

[joaoh82]

Summary

Marketing-side companion to the v0.10.0 release that shipped this morning. SQLR-22's Phase 11 (MVCC + BEGIN CONCURRENT) is end-to-end across the engine + every SDK + the REPL + the bench harness — this PR ships the public-facing announcement.

• New blog post at /blog/shipping-concurrent-writes-mvcc-v010 (full walkthrough — see preview below).
• SITE.version bumped 0.9.1 → 0.10.0 (cascades to every hero / nav / terminal / docs / OG-image reference).
• New #05 Concurrent writes · MVCC tile in the features grid, between Real transactions and JOINs + aggregates.
• New Phase 11 row in the roadmap component as ✅ shipped; "What's next" bullets refreshed.

Closes SQLR-57.

Blog post outline

Same tone as the prior launch posts (shipping-sqlrite-tauri-mcp-sdks, sqlrite-vs-sqlite-benchmarks):

1. The single-writer ceiling — what SQLite's design choice costs.
2. The TL;DR — PRAGMA journal_mode = mvcc; + BEGIN CONCURRENT; snippet.
3. What "concurrent writes" actually means — disambiguates intra-process / cross-process / snapshot reads / row-level conflict detection; what v0.10.0 ships and what it doesn't.
4. The version chain in 30 seconds — diagram of the per-rowid chain + the begin <= T < end visibility rule.
5. Commit-time validation — optimistic CC, six-step commit pseudocode, when to use vs pre-serialize.
6. The retry loop is the whole API — Rust example + the cross-SDK classifier table (is_retryable() / errors.Is(err, ErrBusy) / errorKind === 'Busy' / sqlrite_status_is_retryable).
7. Sibling connections + the Go-SDK story — Connection::connect() plus the cross-pool path registry hack that makes database/sql actually work cross-*sql.DB.
8. Durability + the new WAL frame kind — MvccCommitBatch body diagram, the piggyback-on-existing-fsync trick, WAL format v1 → v3.
9. The REPL is the demo — .spawn / .use / .conns walkthrough with a real Busy retry.
10. What's left out, on purpose — indexes-under-MVCC (Turso also punted), checkpoint drain, cross-process MVCC.
11. What it took — the 10 merged sub-phases (PR feat(engine): Phase 11.1 multi-connection foundation (SQLR-22) #122 → feat(sdk:go): Phase 11.11c — cross-pool sibling shape via path registry (SQLR-22) #134).
12. Try it — install commands per language.

About 2200 words; the rendering picks up at /blog/shipping-concurrent-writes-mvcc-v010 with OG + Twitter cards auto-generated.

Site changes

• src/lib/site.ts — SITE.version = "0.10.0".
• src/components/hero.tsx — "Phases 0–10 shipped" → "Phases 0–11 shipped — concurrent writes live".
• src/components/features.tsx — new tile inserted at implementation of select #5, existing tiles 05-12 renumbered to 06-13; Introduce Slack / Discord / Libera ?  #11 (Six language SDKs) blurb extended to mention sibling handles.
• src/components/roadmap.tsx — new "Phase 11 — Concurrent writes via MVCC (v0.10.0)" entry as done with the sub-phase bullet list; section subtext refreshed; "What's next" updated (HAVING / BETWEEN / scalar functions surfaced; MVCC checkpoint-drain + indexes-under-MVCC carve-outs called out).

Verification

Verified locally before pushing:

• npx tsc --noEmit — clean
• npm run lint — no ESLint warnings
• npm run build — clean Next.js production build; new post landed at /blog/shipping-concurrent-writes-mvcc-v010 with OG + Twitter images
• CI green

Cross-references

• v0.10.0 tag: 937f8b4
• Release pipeline run (succeeded): 25685733621
• Canonical reference the post links into: docs/concurrent-writes.md
• Worked example the post points at: examples/rust/concurrent_writers.rs

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
rust-sqlite	Ready	Preview, Comment	May 12, 2026 4:18am