Skip to content

build(deps): bump github.com/authzed/spicedb from 1.53.1-0.20260612201921-1d5d2c81ab70 to 1.54.0#703

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/github.com/authzed/spicedb-1.54.0
Open

build(deps): bump github.com/authzed/spicedb from 1.53.1-0.20260612201921-1d5d2c81ab70 to 1.54.0#703
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/github.com/authzed/spicedb-1.54.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 23, 2026

Copy link
Copy Markdown
Contributor

Bumps github.com/authzed/spicedb from 1.53.1-0.20260612201921-1d5d2c81ab70 to 1.54.0.

Release notes

Sourced from github.com/authzed/spicedb's releases.

v1.54.0

Security

  • Prevent cache poisoning. The dispatch Check cache key now incorporates check hints. See GHSA-4vrg-r928-h5vv

Added

Changed

  • Cache: switch to otter as the primary cache implementation (authzed/spicedb#3112)
  • Server handles: GRPCDialContext as a handle on the server used deprecated gRPC methods. We modernized it and renamed it to NewClient (authzed/spicedb#3147)

Fixed

  • The watching schema cache (--enable-experimental-watchable-schema-cache) no longer enters permanent fallback on transient watch errors. A new supervisor restarts the watch cycle with bounded exponential backoff and only treats caller-driven cancellation or unsupported-watch as terminal (authzed/spicedb#3134)
  • Watch consumers that request WatchCheckpoints now eventually observe every revision returned by WriteRelationships as a checkpoint. MemDB regressed this in authzed/spicedb#2578 for no-op writes and MySQL never emitted checkpoints at all prior to now. Both now emit a checkpoint at the new revision. (authzed/spicedb#3114)
  • When Query Planner evaluates a union, short-circuit if one of the branches yields a positive un-caveated result (authzed/spicedb#3120)
  • DispatchQueryPlan previously did not try to use the singleflight middleware for check calls. (authzed/spicedb#3119)
  • Fixed regression introduced in 1.53.0. Postgres HeadRevision no longer allocates a new transaction ID on every call (authzed/spicedb#3127)
  • Fixed regression introduced in 1.53.0 for MySQL migration scripts (authzed/spicedb#3129)
  • Query Planner: LookupSubjects no longer returns a subject excluded from a wildcard (e.g. viewer:* - banned) when the exclusion feeds an intersection (experimental --experimental-query-plan ls) (authzed/spicedb#3136)
  • Tracing: When server is shutting down, flush traces. Also, elide the need for setting OTEL_EXPORTER_OTLP_ENDPOINT. (authzed/spicedb#3108)
  • Fixed a LookupSubjects issue in the query planner around the handling of wildcards in compound permissions (authzed/spicedb#3140)
  • MySQL: identifiers (object/subject IDs and relationship counter names) are now stored with a case-sensitive (binary) collation, matching the Postgres, CockroachDB, and Spanner datastores. Previously, identifiers differing only in letter case (e.g. Foo and foo) incorrectly collided in unique indexes and lookups. ⚠️ The migration rebuilds the relation_tuple table in place via ALTER TABLE, which can hold a metadata/table lock for a long time on large datasets — run the upgrade in a low-traffic window, or apply it with an online schema-change tool (e.g. gh-ost). (authzed/spicedb#3161)
  • server.NewConfigWithOptionsAndDefaults now populates Config and its embedded structs with the same defaults as the CLI flags, fixing zero-value behavior when embedding SpiceDB as a library. (authzed/spicedb#3156)

What's Changed

... (truncated)

Changelog

Sourced from github.com/authzed/spicedb's changelog.

[1.54.0] - 2026-06-18

Added

Changed

  • Cache: switch to otter as the primary cache implementation (authzed/spicedb#3112)
  • Server handles: GRPCDialContext as a handle on the server used deprecated gRPC methods. We modernized it and renamed it to NewClient (authzed/spicedb#3147)

Fixed

  • The watching schema cache (--enable-experimental-watchable-schema-cache) no longer enters permanent fallback on transient watch errors. A new supervisor restarts the watch cycle with bounded exponential backoff and only treats caller-driven cancellation or unsupported-watch as terminal (authzed/spicedb#3134)
  • Watch consumers that request WatchCheckpoints now eventually observe every revision returned by WriteRelationships as a checkpoint. MemDB regressed this in authzed/spicedb#2578 for no-op writes and MySQL never emitted checkpoints at all prior to now. Both now emit a checkpoint at the new revision. (authzed/spicedb#3114)
  • When Query Planner evaluates a union, short-circuit if one of the branches yields a positive un-caveated result (authzed/spicedb#3120)
  • DispatchQueryPlan previously did not try to use the singleflight middleware for check calls. (authzed/spicedb#3119)
  • Fixed regression introduced in 1.53.0. Postgres HeadRevision no longer allocates a new transaction ID on every call (authzed/spicedb#3127)
  • Fixed regression introduced in 1.53.0 for MySQL migration scripts (authzed/spicedb#3129)
  • Query Planner: LookupSubjects no longer returns a subject excluded from a wildcard (e.g. viewer:* - banned) when the exclusion feeds an intersection (experimental --experimental-query-plan ls) (authzed/spicedb#3136)
  • Tracing: When server is shutting down, flush traces. Also, elide the need for setting OTEL_EXPORTER_OTLP_ENDPOINT. (authzed/spicedb#3108)
  • Fixed a LookupSubjects issue in the query planner around the handling of wildcards in compound permissions (authzed/spicedb#3140)
  • MySQL: identifiers (object/subject IDs and relationship counter names) are now stored with a case-sensitive (binary) collation, matching the Postgres, CockroachDB, and Spanner datastores. Previously, identifiers differing only in letter case (e.g. Foo and foo) incorrectly collided in unique indexes and lookups. ⚠️ The migration rebuilds the relation_tuple table in place via ALTER TABLE, which can hold a metadata/table lock for a long time on large datasets — run the upgrade in a low-traffic window, or apply it with an online schema-change tool (e.g. gh-ost). (authzed/spicedb#3161)
  • server.NewConfigWithOptionsAndDefaults now populates Config and its embedded structs with the same defaults as the CLI flags, fixing zero-value behavior when embedding SpiceDB as a library. (authzed/spicedb#3156, authzed/spicedb#3170)

Security

  • Prevent cache poisoning. The dispatch Check cache key now incorporates check hints. See GHSA-4vrg-r928-h5vv

[1.53.0] - 2026-05-13

Added

  • Add DispatchExecutor, a query plan executor that is Dispatch-aware and sends subproblems on Alias boundaries (authzed/spicedb#3074)

  • Implement Dispatch caching for query plan execution (authzed/spicedb#3079)

  • Add new optimizer to query planner based on set theory laws for simplifications (authzed/spicedb#3051)

  • Experimental: Add unified schema storage with ReadStoredSchema/WriteStoredSchema APIs for improved schema read performance (authzed/spicedb#2924)

    This feature stores the entire schema as a single serialized proto rather than reading individual namespace and caveat definitions separately, significantly improving schema read performance.

    Migration to unified schema storage is controlled by the --experimental-schema-mode flag, which supports a 4-phase rolling migration:

    1. read-legacy-write-legacy (default) - No change; reads and writes use legacy per-definition storage.
    2. read-legacy-write-both - Reads from legacy storage, writes to both legacy and unified storage. This is the first migration step and backfills the unified schema table.
    3. read-new-write-both - Reads from unified storage, writes to both. Validates the new read path while maintaining backward compatibility.
    4. read-new-write-new - Reads and writes only unified storage. This is the final migration target.

    Deployment:

    • With the SpiceDB Operator:* Configure the operator to roll through stages 1 through 4 in sequence. The operator handles the rolling update of SpiceDB instances at each stage.
    • Without the operator:* Progress through the stages manually by updating the --experimental-schema-mode flag and performing a rolling restart at each stage. You can also take the system down briefly and move directly from stage 1 to stage 4, which runs the full migration in one step.

Changed

Fixed

  • Query plan contexts are written to during recursive calls -- for now, disble dispatch inside recursive calls (authzed/spicedb#3078)

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [github.com/authzed/spicedb](https://github.com/authzed/spicedb) from 1.53.1-0.20260612201921-1d5d2c81ab70 to 1.54.0.
- [Release notes](https://github.com/authzed/spicedb/releases)
- [Changelog](https://github.com/authzed/spicedb/blob/main/CHANGELOG.md)
- [Commits](https://github.com/authzed/spicedb/commits/v1.54.0)

---
updated-dependencies:
- dependency-name: github.com/authzed/spicedb
  dependency-version: 1.54.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the area/dependencies Affects dependencies label Jun 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/dependencies Affects dependencies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants