Add schema version to v2 query schemas - #167
Merged
Merged
Conversation
sqd-query-engine 419b99d requires a catalog to declare `version: v2` and refuses one without it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Add
version: v2to each catalog inquery-schemas-v2/. sqd-query-engine@366ee75 requires it, so the worker in subsquid/worker-rs#79 can't load these catalogs until this is merged. Merge this first.v2.15.0,v2.16.0-rc1) read the v1 catalogs, so they're unaffected.sqd-metadata@419b99d, including underparse_dataset_description_strict.🤖 Generated with Claude Code