Skip to content

Add SpiceDB v1.56.0 to the update graph - #443

Open
ivanauth wants to merge 1 commit into
authzed:mainfrom
ivanauth:fix/issue-442-update-graph-spicedb-v1-56-0
Open

Add SpiceDB v1.56.0 to the update graph#443
ivanauth wants to merge 1 commit into
authzed:mainfrom
ivanauth:fix/issue-442-update-graph-spicedb-v1-56-0

Conversation

@ivanauth

@ivanauth ivanauth commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Fixes #442.

The graph topped out at v1.54.0, and since #434 pinning a version outside the graph is rejected, so v1.56.0 was unreachable by pin or by upgrade. Adds the v1.56.0 node and the v1.54.0 -> >=1.56.0 edge to all five channels; there is no v1.55.x.

SpiceDB v1.56.0 has been out since 2026-07-24, but the update graph
topped out at v1.54.0, and since authzed#434 pinning a version outside the
graph is rejected. There is no v1.55.x release, and the head datastore
migrations are unchanged between v1.54.0 and v1.56.0.

config/update-graph.yaml is left for CI to update after e2e validation.

Signed-off-by: ivanauth <ivan@authzed.com>
@ivanauth
ivanauth force-pushed the fix/issue-442-update-graph-spicedb-v1-56-0 branch from b0284b3 to 73ca135 Compare August 26, 2026 17:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update the update graph to SpiceDB v1.56.0

2 participants