Changelog

What we shipped.

What we shipped, week by week. Rolling release notes straight from main. No marketing-language rewrites.

Subscribe
/changelog/rss.xmlcoming soonGitHub ReleasesFollow @mongoqui
Filter
2026-04-18
build.2026.04.18

Infra & deploy

Per-service deploy scripts and a new account-pinned orchestrator land so every backend service can be shipped independently or in a single coordinated sweep. Dev configs are repointed at the new account. No user-facing changes.

Highlights
  • [Infra]Per-service deploy scripts + account-pinned orchestratord25586c
  • [Infra]Dev configs pointed at the new account0b70301
  • [Docs]Py-backend deployment guide9d0ce09
  • [Docs]Report Builder deployment guide4a00174
2026-04-17
build.2026.04.17

Sharing polish & share-action gating

End-to-end share-action gating lands with elevated-permission checks on every sensitive action (export, delete, and re-run) now all routed through a role verification. Shared report viewer gets a layout pass and the report cards are polished.

Highlights
  • [Security]End-to-end share action gating and elevated permissions961c525
  • [Fix]Shared viewer layout aligned and report cards polished2712190
  • [Fix]Shared-report viz queries repaired, env cookies isolated per domainfe37d69
  • [Fix]Share Report logical fixes and UI/UX pass40e8798
  • [Fix]Auth refresh flow stabilised1f45deb
  • [Feature]Report Builder UI/UX improvements1d04f2f
  • [Infra]CORS origins updated for the new domainb7e8106
2026-04-16
build.2026.04.16

AI Report Assistant · Report Re-Run · Password-protected shares

Three flagship features land on the same day. The AI Report Assistant brings natural-language analytics and schema-aware BI suggestions to Report Builder, powered by AI inference (Llama 3.3 70B). Report Re-Run lets you refresh any report against new data with one click. Password-protected share links add a bcrypt-hashed password + expiry timestamp layer to every public share URL.

Highlights
  • [Feature]AI Report Assistant flow: AI inference + Llama 3.3 70Bcc13afa
  • [Feature]Report Re-Run flow: refresh any report on new data67b25e3
  • [Security]Password protection for public shared report links35b4080
  • [Breaking]Report ID validation moved from ObjectId → UUID formatfd6747d
2026-04-14 → 15
build.2026.04.15

Report share hardening

Four back-to-back fixes close out the remaining share-access edge cases: a URL-key change, header handling for API calls, and an auth-refresh repair sweep. Report mail delivery is fixed and wrangler.toml gets a cleanup pass across services.

Highlights
  • [Fix]Report URL key change43ee9a4
  • [Fix]Report headers fix for API calls (then reverted pending better path)dfa29f7
  • [Fix]Report share access fix20e66b2
  • [Fix]Reports and report-share auth issues resolvedb7ef2e6
  • [Fix]Report mail delivery repaired535af6c
  • [Infra]wrangler.toml cleanup3feecfc
2026-04-07 → 09
build.2026.04.09

Shared connections & shared reports

Shared-connection pagination, role assignment, and invitation flows all get fixes. Saved queries are stabilised (collection name + save flow), JSON export and object storage exports are repaired, and file-service export headers are handled for the new S3-compatible path.

Highlights
  • [Fix]Shared-connection pagination and user listd68f46c
  • [Fix]Shared-connection role assignmentc730e69
  • [Fix]Invitation flow for shared connections03c7695
  • [Fix]Shared-connection edge cases818a9e3
  • [Fix]Report URL public-view hardening3e4a781
  • [Fix]JSON export, object storage export, file-service export5fedc2b
  • [Fix]Saved query collection name + save flowf21afb3
  • [Fix]Query history route7b67ea7
  • [Fix]S3 request headers handled for file reportsf5e4892
  • [Infra]Current-tier restriction with org removed for shared-connection pathf0fc696
  • [Infra]CORS fixb4a0723
2026-04-01 → 06
build.2026.04.06

Shell, cached response & refresh-token stability

Shell and cached-response paths get a performance refactor. Py-worker routing is updated. The big win of the week is refresh-token stability. MongoQUI used to fail after days of idle due to a stale refresh token; now the refresh flow is cached, scoped out of login, and wired through py-backend.

Highlights
  • [Feature]Shell and cached-response performance refactor712bbf1
  • [Fix]Refresh-token handling for py-backend: no more connection errors after idle daysf9ad289
  • [Fix]Login path excluded from refresh-token flow13a8588
  • [Infra]Py-worker routing updates4be7022
  • [Fix]Connection fix post-refresh-token workeda5d13
2026-03-30
build.2026.03.30

Cloud backend container + database migration

The architecture release. Py-backend moves into a cloud container, which unlocks per-user state, warm starts, and cheaper long-lived connections. The control plane migrates to our own database. Internal service-secret enforcement is now mandatory across service bindings.

Highlights
  • [Breaking]Py-backend cloud container servicebfeb46a
  • [Breaking]Supabase → own database migration9318b66
  • [Security]Internal-service-secret now mandatory across service bindings490b133
  • [Security]Cached-response auth added7bb524e
  • [Infra]Allowed origins tightened85dbf59
  • [Fix]Audit Report issues handled4577aba
  • [Fix]Query historyc584f9d
2026-03-28 → 31
build.2026.03.31

Shell & developer docs

Shell connection and query paths get an optimisation pass: faster first-query latency, fewer stale sockets. Detailed developer documentation ships for py-backend and internal integration.

Highlights
  • [Feature]Shell connection and query optimisation0e81b53
  • [Docs]Detailed developer documentation9a0b0a2
  • [Docs]Py-backend document3b37343
  • [Infra]Config updatesf0cc434
Cadence

We release weekly on Thursdays (UAE time). Dev builds are continuous.

Every push to main becomes a rolling build. Big feature blocks get their own dated entry. Marketing-free. Just what shipped.

Still to come

Open questions we’re working.

  • 01InfraPublic RSS feed at /changelog/rss.xml
  • 02FeaturePre-release edge channel toggle in Settings → Updates
  • 03DocsPer-release contributor bylines
  • 04InfraNamed semver cut at v0.2.0
FAQ

Release cadence questions.

We ship to main continuously. Public dev builds roll out roughly weekly and auto-update silently for anyone installed from updates.mongoqui.com. Big feature blocks (AI Report Assistant, Durable-Object py-backend) get their own dated entry.
Ship with us

Start trying MongoQUI.

Auto-updates from main. Your install gets every release in this log as soon as it ships.