ci: publish models index via GitHub Releases (index-v* tags) - #57
Merged
Conversation
Runtimes must pin DEFAULT_INDEX_URL to a Release asset + sha256 sidecar — never raw.githubusercontent.com, never main. Workflow release-index.yml stages models-index.yaml and its .sha256 on every index-v* tag (or workflow_dispatch).
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.
Production data channel for the model index is GitHub Releases — same
pattern as maps IR artifacts and model weight zips. raw.githubusercontent.com
is never used for any data path.
stages models-index.yaml + models-index.yaml.sha256 and attaches
them to a GitHub Release.
sidecar verification step every runtime must implement.
Follow-up: cut index-v1 from main, then retarget DEFAULT_INDEX_URL in
interscript-ts / secryst crystals to the Release download URL with
sidecar sha256 verification.