Add SpiceDB v1.56.1 to the update graph - #443
Open
ivanauth wants to merge 2 commits into
Open
Conversation
miparnisari
previously approved these changes
Aug 26, 2026
ivanauth
force-pushed
the
fix/issue-442-update-graph-spicedb-v1-56-0
branch
from
August 26, 2026 17:41
b0284b3 to
73ca135
Compare
ecordell
previously approved these changes
Sep 1, 2026
SpiceDB v1.56.1 has been out since 2026-08-21, 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.1. config/update-graph.yaml is left for CI to update after e2e validation. Signed-off-by: ivanauth <ivan@authzed.com>
secrets.AUTHZED_BOT_PAT is not exposed to pull requests from forks, so actions/checkout failed with "Input required and not supplied: token" before any test ran. Fall back to the workflow token for the checkout and only attempt to push the validated graph when the PAT is present. Signed-off-by: ivanauth <ivan@authzed.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ivanauth
force-pushed
the
fix/issue-442-update-graph-spicedb-v1-56-0
branch
from
September 2, 2026 17:40
73ca135 to
37cb6a1
Compare
ivanauth
changed the title
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Sep 3, 2026
|
@tstirrat15 could you readd to the merge queue so this will be merged soon? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #442.
The graph topped out at v1.54.0, and since #434 pinning a version outside the graph is rejected, so v1.56.x was unreachable by pin or by upgrade. Adds the v1.56.1 node and the
v1.54.0 -> >=1.56.1edge to all five channels; there is no v1.55.x, and v1.56.1 is the latest patch of that minor (matching the existing latest-patch-per-minor convention, e.g. v1.51.1). The head datastore migrations are unchanged between v1.54.0 and v1.56.1 for all four engines.Also fixes the E2E job, which could never run for a graph change opened from a fork:
secrets.AUTHZED_BOT_PATis not exposed to fork pull requests, soactions/checkoutfailed withInput required and not supplied: tokenbefore any test ran. The checkout now falls back to the workflow token, and the "Commit validated update graph" step only runs when the PAT is actually present. For fork PRs the new edges are still validated by E2E;config/update-graph.yamlgets committed by the push-to-main run after merge.