Skip to content

v0.4.0 — Resource lifecycle and fixed subscription TTL

Choose a tag to compare

@github-actions github-actions released this 23 Oct 12:37
· 50 commits to main since this release
932b078

MQLite v0.4.0 completes the reviewed resource-lifecycle work for queues and subscriptions, adds fixed subscription lifetimes, and removes the withdrawn public queue Generation contract.

Important

v0.4.0 uses schema token 7. There is no in-place migration from the schema-5 database used by v0.3.x. Stop writers, take a consistent backup, account for retained messages and managed keys, preserve the matching old binary/database pair, and start v0.4.0 with a fresh database. Schema 6 belonged only to untagged development builds and is refused as well.

Resource lifecycle

  • Queue deletion remains empty-only by default. force=true explicitly authorizes discarding retained work through bounded, restart-safe cleanup.
  • Subscriptions support the same empty-only and explicit-force deletion contract, with lifecycle-aware paginated inventory and a configurable active-plus-deleting capacity bound.
  • Subscription TTL is a fixed lifetime from first creation. Retries, filter updates, publishing, receiving, and settlement never extend it. Expiry is advance authorization for forced cleanup.
  • Resource names remain the public identity. One owner must serialize deletion with same-name recreation and reconcile uncertain outcomes before reusing a name.
  • For frequent request/reply traffic, prefer a stable reply subscription plus correlation IDs. Use temporary subscriptions and TTL as a bounded cleanup backstop, not as the default high-rate pattern.

Operations and observability

  • Local file brokers isolate observation reads on one read-only WAL connection and share expensive all-queue snapshots for about 10 seconds.
  • Global observation aggregation performs one state classification per retained message while preserving exact counters.
  • Destructive broker operations emit safe request IDs and reconciliation evidence without logging credentials, message bodies, or generated secrets.
  • Prometheus aliases mqlite_queue_total and mqlite_queue_oldest_message_age_ms have been removed. Use mqlite_queue_retained_messages and mqlite_queue_oldest_message_age_seconds.
  • RPC bodies now require exactly one non-null JSON object.
  • Turso/libSQL receive claims use the reviewed write-first transaction order. Multiple brokers sharing one database remain unsupported.

Withdrawn v0.3.3

v0.3.3 remains withdrawn and unsupported as a whole. v0.4.0 carries the Go module retraction and replaces its public queue Generation contract. Historical v0.3.3 artifacts remain available only for audit, reproduction, and recovery; do not deploy them.

Get started

The release commit is 932b078121744de895362d3778e2ed7037f67d81. Its required main CI run completed successfully with all 13 jobs in one attempt before the tag was created.