Shipped · Databases

What authzed/spicedb shipped

The public repository of Authzed · github.com/authzed/spicedb

Written by FoxPlug from the repository's own releases; not affiliated with Authzed. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/authzed/spicedb; Authzed did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

See the update FoxPlug writes for spicedb, free

Week of October 26, 2026

What shipped

Why it matters

This week fixed several reliability problems that affect running clusters: read pool deadlocks, invalid cursors during paginated LookupResources, stale certificate authorities after rotation, and cache entries that never aged out on their own. Schema writes also stopped stripping annotations from unchanged definitions, which removes a regression introduced in v1.49.0. Alongside those fixes, query planning gained reusable signals and better isolated, tested optimizations.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: fixed read pool deadlocks and LookupResources cursor locking, stopped schema writes from stripping annotations on unchanged definitions, made dispatch cache entries expire a fixed TTL after write, and reload certificate authorities on rotation.

Post for LinkedIn

This week in SpiceDB: several fixes for issues that show up in running clusters. Nested connection acquisition could deadlock the read pool, and paginated LookupResources could fail with invalid cursor errors when secondary dispatchers were configured; both are fixed. Schema writes no longer strip aliasing_relation and canonical_cache_key annotations from unchanged definitions. Dispatch cache entries now expire a fixed TTL after they are written rather than on last access, and certificate authorities are reloaded when they rotate on disk instead of staying pinned for the process lifetime. The query planner gained reusable planning signals tied to compatible datastore revisions, and each optimization now lives in its own documented, tested subpackage.

Week of October 19, 2026

What shipped

Why it matters

This week brings the v1.57.0 release with an experimental full relation cache that can serve reads of a hot object from cache, including empty answers, without a datastore query. It also makes relationship filtering on a permission fail with a clear error instead of an opaque type-system error. Two fixes address correctness and operations: wildcard cache keys are now qualified per definition, and the CockroachDB garbage collection window follows the relationships table's zone config.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

SpiceDB v1.57.0 is out: an experimental full relation cache (off by default) serves hot object reads, including empty answers, without a datastore query. Also: clearer errors when filtering relationships on a permission, wildcard cache keys qualified by definition, and the Cockro

Post for LinkedIn

SpiceDB v1.57.0 is released. It adds an experimental full relation cache, enabled with an experimental flag and off by default. It caches the complete relationship set of a hot object at one revision and serves reads from it, including empty answers, with no datastore query. This week also fixes relationship filtering. ReadRelationships and DeleteRelationships now return a clear error when a filter names a permission rather than failing deep in the type system with an opaque error. The wildcard-check cache is now keyed by definition as well as relation, so a result for one type cannot hide the wildcard in another type with a relation of the same name. On CockroachDB, the garbage collection window now comes from the zone configuration of the relationships table instead of the cluster-wide d

Week of October 5, 2026

What shipped

Why it matters

This week is mostly about correctness in edge cases: subject filters in Watch, hedging cancellation timing, and canceled hedged or cursor-locked dispatches now behave consistently. That means fewer surprising mismatches between Watch and the datastores, and clearer errors when a request is canceled. The subtraction change also makes wildcard exclusions cheaper for LookupSubjects.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Fix week: Watch follows datastore ellipsis filter behavior, hedging cancellations are no longer lost, canceled hedged and cursor-locked dispatches return context errors, and wildcard exclusions in LookupSubjects build once instead of growing a list.

Post for LinkedIn

This week brought several correctness fixes and one performance change. Watch now applies ellipsis-only subject filters the way the datastores do, matching only the ellipsis relation unless NonEllipsisRelation is set. A hedging delay cancellation that arrives before the sleep is no longer lost, so the primary dispatcher can proceed. Canceled hedged dispatches for Check and cursor-locked LookupResources2 now return the context error. Separately, SubtractAll now builds the wildcard exclusion list once, keeping exclusion construction linear while preserving caveat expressions and resource provenance.

Week of September 28, 2026

What shipped

Why it matters

This week includes correctness fixes for the experimental query planner and dispatch system, addressing recursive relations, reflexive edges, and cancellation handling. Performance improvements for relationship deletion and proper timeout configuration ensure the system behaves predictably at scale.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: query planner correctness fixes for recursive relations and reflexive edges, dispatch cancellation handling, and DeleteRelationships performance improvements.

Post for LinkedIn

SpiceDB improvements this week focus on reliability and performance: fixed correctness bugs in recursive relation handling and reflexive identity resolution in the query planner, resolved dispatch cancellation errors that could cause cache inconsistency, improved DeleteRelationships performance with limit queries, and fixed dispatch-upstream-timeout configuration not reaching outbound dispatches.

Week of September 21, 2026

What shipped

Why it matters

This week focused on test reliability and performance. Parallel test execution uncovered and fixed multiple datastore bugs in MemDB and Postgres that would only manifest under concurrent load. CI improvements significantly reduced build times while the new bulk deletion API addresses practical limitations when operating at scale.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: cursored bulk deletion for large relationship sets, SortKeyRevision for ordered datastores, parallel test suites (+bug fixes), and 3x faster builds.

Post for LinkedIn

SpiceDB shipped several improvements this week focused on reliability and performance. We added cursored bulk relationship deletion to handle large-scale deletions efficiently, introduced SortKeyRevision for ordered key-value stores, and enabled parallel test execution—uncovering and fixing multiple datastore concurrency bugs in MemDB and Postgres. CI builds are now 3x faster. These changes address real constraints when operating at scale.

More from authzed/spicedb on GitHub

Merged pull requests

Weeks with too little public activity are left out rather than filled in. Last updated 2026-11-03.

Is this your repo? Ask us to remove this page.