runtime README: TypeScript crystal is npm 'secryst' - #17
Merged
Conversation
Contributor
Author
|
The failing metrics-provenance check is pre-existing on main (failed at 4220af1, the base of this PR; passed at 70065b2 before it) and unrelated to this docs-only diff: it cannot find the tha-g2p-base-1.0 anchor in RESULTS.md. The distillation workspace has the compatible metrics-sources.yaml / docs/RESULTS.md changes uncommitted — merging this PR is safe once that fix lands; no admin-merge bypass. |
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.
What
Follow-through on the crystal naming: the TypeScript package publishes
as bare
secryston npm (verified free; symmetry withpip install secrystandgem 'secryst'). Updates the runtimeREADME's crystal-family references. Docs-only.