Update SpiceDB proposed graph to v1.54.0#438
Open
tstirrat15 wants to merge 2 commits into
Open
Conversation
tstirrat15
force-pushed
the
chore/bump-spicedb
branch
from
193e435 to
8372b59
Compare
tstirrat15
force-pushed
the
chore/bump-spicedb
branch
from
8372b59 to
feea27a
Compare
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
2 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.
Note: this is a copy of #435. The automation needs to be first-party because it's going and committing the validated update graph.
Description
Update the proposed SpiceDB upgrade graph to include v1.54.0 across the supported datastore channels.
This updates tools/generate-update-graph/main.go with the new release state v1.54.0, then regenerates proposed-update-graph.yaml.
Testing
I've regenerated the graph using go generate ./tools/generate-update-graph/main.go and ran the tests.