Repository navigation
Bump graphql_engine to main for the indicator FK migration - #139
Merged
Merged
Conversation
Picks up 1771200018000_response_variable_standard_variable_fk and the metadata move of the four array relationships onto modelcatalog_standard_variable, merged as mintproject/graphql_engine#15. Also picks up the cascade migration (#14), which the pointer had not yet caught up with.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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.
Moves the
graphql_enginesubmodule pointer from0d74aa1to06492bd(main).It picks up two merged PRs:
1771200018000_response_variable_standard_variable_fk,the schema half of Variables step cannot save any indicator: it writes a standard-variable URI into a column that references the legacy variable table #106, plus the metadata move of four array relationships onto
modelcatalog_standard_variable.not yet caught up with.
Pointer only; no other file changes.
Applying the migration to a running deployment is #136 —
helm upgradedoes not runmigrations, and migrations are baked into the hasura image, so the image tag has to move
before
deploy-hasura.shcan see this one.