fix: pin model index to GitHub Releases + verify sha256 sidecar - #47
Merged
Conversation
DEFAULT_INDEX_URL now points at the index-v1 Release asset (models-index.yaml). HTTP index fetches require and verify the sibling .sha256 sidecar before parsing — never raw.githubusercontent.com. Local SECRYST_INDEX paths are unchanged. Bumps to 3.1.0.
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.
raw.githubusercontent.com is never used for any data path. The model
index is a GitHub Release asset, same channel as maps IR and model
weights.
https://github.com/interscript/interscript-ml/releases/download/index-v1/models-index.yaml
.sha256sidecar andreject on mismatch / missing / malformed
Depends on interscript/interscript-ml index-v1 release (already live).
Sibling crystals (secryst-ts/py/ruby) get the same pin in follow-up PRs.