Repository navigation
feat: add versioned SDK-backed compatibility catalog - #1
Merged
Merged
Conversation
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing. Review the Copilot code review billing settings.
This was referenced Oct 18, 2026
igorls
changed the title
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.
Add an opt-in versioned compatibility catalog alongside the unchanged legacy catalog. Declarations use the canonical SDK manifest validator; tested sets require exact source/version pins, evidence URLs and eligibility for the pinned core/SDK/engine environment.
The checked-in v1 catalog stays empty until real component releases are qualified. Includes a synthetic fixture, six public validator/CLI regressions, a bounded consumer audit and explicit legacy migration policy. The tooling depends on the reviewed SDK development commit, not a registry release or local file path.
Validation: clean pinned Git dependency installation, six tests, versioned and legacy catalog checks, Markdown links and whitespace passed locally. Independent Standards and Spec reviews found no issues. Legacy catalog.json is byte-identical. CI verifies the committed catalog on Node 22.
Refs eosrio/hyperion-tools#19. Metadata validation does not establish runtime qualification, verify downloaded artifacts or trigger executable updates.