Skip to content

Releases: authzed/spicedb

v1.15.0

22 Nov 18:46
7f3f207
Compare
Choose a tag to compare

Upgrade Notes

Warning
This is release includes changes for dispatching, which can result in an increased error rate during rollout. To avoid, deploy as a distinct cluster and switch over your load balancer(s)

CockroachDB, Spanner, MySQL, Postgres

(no migrations from v1.14.1)

What's Changed

Docker Images

This release is available at:

  • authzed/spicedb:v1.15.0
  • quay.io/authzed/spicedb:v1.15.0
  • ghcr.io/authzed/spicedb:v1.15.0
  • authzed/spicedb:v1.15.0-debug
  • quay.io/authzed/spicedb:v1.15.0-debug
  • ghcr.io/authzed/spicedb:v1.15.0-debug

New Contributors

Full Changelog: v1.14.1...v1.15.0

v1.14.1

07 Nov 19:52
bb7b2de
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.14.0...v1.14.1

Docker Images

This release is available at authzed/spicedb:v1.14.1, quay.io/authzed/spicedb:v1.14.1, ghcr.io/authzed/spicedb:v1.14.1

v1.14.0

03 Nov 16:47
634952f
Compare
Choose a tag to compare

Highlights

  • Memory management for caching vastly improved by more accurately tracking the size of cache entries
  • Postgres datastore rewritten with massive improvements to write performance
  • Experimental caveats support
  • Massive performance improvement for LookupResources
  • GemFury DEB & RPM repositories are now available for SpiceDB releases

Upgrade Notes

Warning
This is release includes migrations for all datastores, but a more complex migration for Postgres.
You must have already upgraded to v1.13.0 before upgrading to v1.14.0.
To learn more about migrations, see the migration documentation.
To automate migrations, Kubernetes users can run the SpiceDB Operator.

CockroachDB, Spanner, MySQL

CockroachDB, Spanner, MySQL datastore users can run the command spicedb migrate head from a SpiceDB v1.14 binary to migrate a v1.13 cluster. This may result in a brief latency spike, but will otherwise cause no downtime. After the migration is complete, v1.13 processes can be replaced with v1.14 ones.

Postgres

PostgreSQL users have two options: zero downtime or not.

Downtime

  1. Ensure SpiceDB v1.13.0 was running
  2. Shut off SpiceDB in all clusters
  3. Run spicedb migrate head using SpiceDB v1.14
  4. Rollout v1.14 to your cluster(s)

Zero-downtime

  1. Ensure SpiceDB v1.13.0 is currently running
  2. Run spicedb migrate add-xid-columns using SpiceDB v1.14
  3. Rollout v1.14 to your cluster(s) with the following flag: --datastore-migration-phase=write-both-read-old
  4. Once the rollout is fully complete, run spicedb migrate add-xid-constraints using SpiceDB v1.14
  5. Rollout v1.14 to your cluster(s) with the following flag: --datastore-migration-phase=write-both-read-new
  6. Once the rollout is fully complete, run spicedb migrate drop-id-constraints using SpiceDB v1.14
  7. Rollout v1.14 to your cluster(s) with the --datastore-migration-phase flag removed

What's Changed

Full Changelog: v1.13.0...v1.14.0

Docker Images

This release is available at authzed/spicedb:v1.14.0, quay.io/authzed/spicedb:v1.14.0, ghcr.io/authzed/spicedb:v1.14.0

v1.13.0

04 Oct 18:26
v1.13.0
ddce492
Compare
Choose a tag to compare

Highlights

  • Dispatched checks are now batched performed improving performance
  • Protobuf serialization is now much faster by using vtprotobuf to avoid reflection
  • Dispatch API is now compressed with Snappy
  • Cache sizes can now be configured with percentages of free memory

Warning
This release contains a change to the internal dispatch API, which means that v1.13.0 and v1.12.0 can not dispatch to each other during a rolling upgrade. To upgrade without downtime, run these as separate Kubernetes services, or disable dispatch before upgrading.

What's Changed

Full Changelog: v1.12.0...v1.13.0

Docker Images

This release is available at authzed/spicedb:v1.13.0, quay.io/authzed/spicedb:v1.13.0, ghcr.io/authzed/spicedb:v1.13.0

v1.12.0

09 Sep 17:03
0148743
Compare
Choose a tag to compare

Highlights

  • new lookupsubjects RPC answers the question "which subjects have a given permission over a specific resource?"
  • CRDB Store now exposes prometheus metrics for the connection pool
  • new debug containers now being published, which includes busybox. This is convenient for development environments that require a shell
  • PGX driver no longer logs on debug by default, cleaning up SpiceDB's info level
  • CRDB datastore now properly supports connection draining procedures
  • added configurable limits for write and delete relationship APIs
  • leaner and more secure docker images based on distroless.dev

What's Changed

Docker Images

This release is available at:

  • authzed/spicedb:v1.12.0
  • quay.io/authzed/spicedb:v1.12.0
  • ghcr.io/authzed/spicedb:v1.12.0
  • authzed/spicedb:v1.12.0-debug
  • quay.io/authzed/spicedb:v1.12.0-debug
  • ghcr.io/authzed/spicedb:v1.12.0-debug

New Contributors

Full Changelog: v1.11.0...v1.12.0

v1.11.0

04 Aug 16:17
a30aca3
Compare
Choose a tag to compare

Warning
This release contains a change to the internal dispatch API, which means that v1.10.0 and v1.11.0 can not dispatch to each other during a rolling upgrade. To upgrade without downtime, run these as separate Kubernetes services, or disable dispatch before upgrading.

Highlights

  • Check requests can now be traced using the zed CLI using zed permission check --explain
  • serve-testing now supports HTTP
  • Performance improvements for LookupResources, WriteSchemas, and dispatch in general
  • The Watch API is disabled automatically if CRDB datatstores don't support Change Feeds

What's Changed

Full Changelog: v1.10.0...v1.11.0

Docker Images

This release is available at authzed/spicedb:v1.11.0, quay.io/authzed/spicedb:v1.11.0, ghcr.io/authzed/spicedb:v1.11.0

v1.10.0

27 Jul 17:20
694a76f
Compare
Choose a tag to compare

Upgrade Notes

Warning
This is release includes migrations for Postgres and MySQL datastores that adds a column to the namespace table.

Highlights

  • Enabled the ability to safely use Postgres read replicas
  • Added a webassembly interface for devtools
  • Fixed namespaces not being garbage collected for Postgres & MySQL datastores
  • Added health checking and Watch service to HTTP API
  • Added seamless TLS certificate rotation

What's Changed

New Contributors

Full Changelog: v1.9.0...v1.10.0

Docker Images

This release is available at authzed/spicedb:v1.10.0, quay.io/authzed/spicedb:v1.10.0, ghcr.io/authzed/spicedb:v1.10.0

v1.9.0

21 Jun 18:15
c6f3b29
Compare
Choose a tag to compare

Warning
This release contains a change to the internal dispatch API, which means that v1.8.0 and v1.9.0 can not dispatch to each other during a rolling upgrade. To upgrade without downtime, run these as separate Kubernetes services, or disable dispatch before upgrading.

What's Changed

Full Changelog: v1.8.0...v1.9.0

Docker Images

This release is available at authzed/spicedb:v1.9.0, quay.io/authzed/spicedb:v1.9.0, ghcr.io/authzed/spicedb:v1.9.0

v1.8.0

01 Jun 19:18
a8c3809
Compare
Choose a tag to compare

Highlights

  • New, speedier LookupResources implementation
  • New datastore interface improves performance for all datastores
  • MySQL driver now has feature parity with the Postgres driver

What's Changed

New Contributors

Full Changelog: v1.7.1...v1.8.0

Docker Images

This release is available at authzed/spicedb:v1.8.0, quay.io/authzed/spicedb:v1.8.0, ghcr.io/authzed/spicedb:v1.8.0

v1.7.1

03 May 13:17
53f8741
Compare
Choose a tag to compare

This is a bugfix release for 1.7.0

What's Changed

Full Changelog: v1.7.0...v1.7.1

Docker Images

This release is available at authzed/spicedb:v1.7.1, quay.io/authzed/spicedb:v1.7.1, ghcr.io/authzed/spicedb:v1.7.1