Upgrade to EdgeQuake v0.32.0
Upgrade to EdgeQuake v0.32.0
Section titled “Upgrade to EdgeQuake v0.32.0”From: v0.31.0 · To: v0.32.0 · CD: GHCR (
edgequake,edgequake-frontend,edgequake-postgres,edgequake-keycloak)
This minor release hardens tenant-scoped data access and improves query and convert reliability. The schema moves from 166 to 168. Run migrate before /ready returns 200.
From 0.30.0 or older, migrate to 166 first (upgrade-to-0.31.0.md), then apply this release.
Both new migrations are additive (expand phase):
- 167 creates the
edgequake_tenant_accessrole (NOLOGIN,NOBYPASSRLS) and turns onFORCE ROW LEVEL SECURITYfor content tables. - 168 adds
users.failed_login_attemptsandusers.locked_untilwithIF NOT EXISTS.
demo.edgequake.com: this cut installs the 0.32.0 API and WebUI. Decision mode stays a preview with uncalibrated gates. Password auth remains the demo default. SSO stays opt-in from 0.30.0.
Highlights
Section titled “Highlights”| Area | What changed |
|---|---|
| Schema | 167: tenant RLS role and policies; 168: identity lockout columns |
| Query | Scoped graph-read timeouts; incremental RAG streaming |
| Convert | Reliability fixes for vision and PDF convert timeouts |
| Benchmark | Same 2026-08-15 medical-mid attestation as 0.31.0; query deadlines, graph-read scope and streaming were not re-scored |
Upgrade path
Section titled “Upgrade path”%%{init: {"theme":"base","themeVariables":{"primaryColor":"#E0E7FF","primaryBorderColor":"#6366F1","primaryTextColor":"#1E1B4B","secondaryColor":"#D1FAE5","secondaryBorderColor":"#10B981","secondaryTextColor":"#064E3B","tertiaryColor":"#FEF3C7","tertiaryBorderColor":"#F59E0B","tertiaryTextColor":"#6B7A90","lineColor":"#7A889C","clusterBkg":"rgba(99,102,241,0.07)","clusterBorder":"#A5B4FC","noteBkgColor":"#FEF9C3","noteTextColor":"#422006","textColor":"#6B7A90","titleColor":"#6B7A90","signalColor":"#7A889C","signalTextColor":"#6B7A90","loopTextColor":"#6B7A90","edgeLabelBackground":"#F1F5F9","actorLineColor":"#94A3B8"}}}%%
%% eq-theme:v1
flowchart TB
A["Running 0.31.0 (schema 166)"] --> B["Pull 0.32.0 images"]
B --> C["migrate applies 167: tenant access role and RLS"]
C --> D["migrate applies 168: lockout columns on users"]
D --> E["Start the 0.32.0 API"]
E --> F{"schema.latest_version 168 and pending_count 0?"}
F -->|yes| G["Upgrade complete"]
F -->|no| H["Run migrate again and check the logs"]
Notice that the final check confirms both migrations applied before you call the upgrade done.
Upgrade sequence
Section titled “Upgrade sequence”# Already on 0.31.0 (schema 166)EDGEQUAKE_VERSION=0.32.0 docker compose pull# migrate job or `edgequake migrate` (applies 167 and 168), then the APIEDGEQUAKE_VERSION=0.32.0 docker compose up -dVerify
Section titled “Verify”curl -sf localhost:8080/health | jq '{version, schema}'# expect version "0.32.0", schema.latest_version 168 and pending_count 0Residuals (not release blockers)
Section titled “Residuals (not release blockers)”- SPEC-001 Acc was not re-run. Query deadlines, graph-read scope and streaming changed after the 2026-08-15 pack.
- Decision extraction is still a preview with uncalibrated gates. See upgrade-to-0.31.0.md.