Repository navigation
PrismNote v1.11.0
Real local SQL execution + real Docker sandbox
This release makes two core, previously-stubbed features genuinely real:
Local/remote SQL execution (crates/server/src/db/executor.rs):
- SQLite — real, embedded, always works. Verified end-to-end through
the live HTTP API:CREATE TABLE/INSERT/SELECT, with the
resulting file independently checked with thesqlite3CLI. - DuckDB — real, embedded (bundled, compiled from source, no system
library needed). - PostgreSQL — real, via
sqlx. Verified end-to-end against a live
Postgres container, independently checked withpsql. - MySQL — real, via
sqlx. Covered by an integration test that runs
for real against a live MySQL container. - MongoDB is explicitly not implemented (returns a real error, not a fake
success).
Docker sandbox code execution (crates/server/src/docker_executor.rs):
Every execution gets a brand-new, disposable container: no network access
by default, memory/CPU/process-count limits, a wall-clock timeout that
force-kills and cleans up, real stdout/stderr/exit-code capture. Verified
via real Docker containers, including a genuine OOM-kill test and a
genuine "no network access" test, and again through the live
/api/docker/sandbox/execute HTTP route.
Also in this release:
make buildnow actually produces a binary that serves the UI (builds
the frontend first, since the backend embeds it) — this was the root
cause behind prior "make build fails" reports.- Notebook ownership/permission checks are now backed by the real
database instead of always granting every user Owner access. - Frontend gets a real vitest suite (111 tests) and is wired to the real
SQL backend. - Version reconciled: frontend was at 1.7.0, backend at 1.10.0; both are
now 1.11.0.
Release asset note: only prismnote-macos-arm64 is attached — this
environment has just the aarch64-apple-darwin Rust toolchain installed,
with no cross-compilation targets for Linux/Windows/Intel-Mac. The
release-assets/ binaries already committed to the repo for other
platforms are stale (built 26 Jul, predate this release) and were not
regenerated here; a CI-based cross-platform build is the right way to
refresh those rather than hand-building them without the ability to test
them.
Built and tested on this machine: cargo test --workspace --release
(101 passed / 0 failed, run against live Postgres/MySQL containers),
cargo fmt --check (clean), npm test in frontend/ (111 passed).