Skip to content

runtime: deprecate interscript-ml in favor of secryst; index default -> index-v6 release channel - #236

Merged
ronaldtse merged 1 commit into
mainfrom
fix/runtime-index-v6-deprecate
Oct 3, 2026
Merged

ronaldtse merged 1 commit into
mainfrom
fix/runtime-index-v6-deprecate

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

Closes the runtime-consolidation gaps 3+4 (decision: secryst is the canonical Python package).

  • Index default fixed: DEFAULT_INDEX_URL was raw.githubusercontent.com/main/models.yaml - raw.githubusercontent is never a data path in the distribution contract (canonical channel: GitHub Releases + sha256 sidecar). Now pinned to index-v6 with an exact-pin test (the runtime had no pin test at all). All three crystals now default to index-v6: TS (npm 5.5.1), secryst-py (PR feat(distill): WO07 logit-distillation runner (Hebrew base->small case study) #5), gem (secryst PR metrics: finish ara-diac-small full-set provenance entries #55).
  • Deprecation metadata: README banner + pyproject 0.1.2 with Development Status :: 7 - Inactive and a deprecated description pointing at pypi.org/project/secryst. runtime/ stays as frozen provenance (the crystal family's origin, per TODO.secryst-rebrand/03).

The 0.1.2 release to PyPI is the owner's action (twine with your ~/.pypirc, or say the word and I will wire an OIDC trusted-publishing workflow like secryst-py's - no tokens; then you push the tag).

…ult to index-v6 release channel

- DEFAULT_INDEX_URL was raw.githubusercontent.com (never a data
  channel; the contract is Releases + sha256 sidecar) - now pinned to
  index-v6 with an exact-pin test, matching all three crystals
- README deprecation banner + pyproject 0.1.2 with Inactive/deprecated
  metadata: the canonical Python crystal is 'secryst'
@ronaldtse
ronaldtse merged commit 6e21118 into main Oct 3, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant