fix(config): set subgraph start blocks so Goldsky can deploy - #67
Merged
Merged
Conversation
An empty VAULT_START_BLOCK rendered as null in the manifest, which Goldsky rejects as an invalid i32.
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.
Summary
VAULT_START_BLOCKfor dev and both subgraph start blocks for prd, which were left as TODOs after feat: single source of truth for public config in config/<env>.env #65.startBlockrendered asnullin the vault manifest; Goldsky rejectedcollateral-vault/v1.0.179-devwithinvalid type: null, expected i32.Test plan
indexer/subgraph.yamlhas a numericstartBlock(CI prints the file in Prepare subgraph configuration).dev.