chore(registry): publish marketplace registry update#653
Conversation
| "variants": [ | ||
| { | ||
| "accelerator": "cuda", | ||
| "url": "https://github.com/streamer45/streamkit/releases/download/plugin-whisper-v0.3.0/whisper-0.3.0-cuda-bundle.tar.zst", | ||
| "sha256": "1ed98fbb2020a405dda228d59854ebb39d94a083921bdacb77373631ee2e496e", | ||
| "size_bytes": 108047246 | ||
| } | ||
| ], |
There was a problem hiding this comment.
📝 Info: In-place modification of already-published 0.3.0/0.4.0 manifests
This PR adds variants (CUDA bundles) to manifests whose version numbers are unchanged (helsinki 0.3.0, kokoro 0.3.0, matcha 0.3.0, sensevoice 0.3.0, vad 0.4.0, whisper 0.3.0) and re-signs them with new timestamps. I verified all regenerated signatures validate against the modified manifest bodies using the repo public key (dist/registry/streamkit.pub), so clients performing signature verification will accept them. Mutating an already-published version in place (rather than bumping the version) is the only mildly surprising aspect — any client that cached the old signature/manifest will see a mismatch — but this appears intentional since the release tooling regenerated both mirrors and both signature files consistently.
Was this helpful? React with 👍 or 👎 to provide feedback.
Debug
| "models": [ | ||
| { | ||
| "id": "parakeet-tdt-0.6b-v3-int8", | ||
| "name": "Parakeet TDT 0.6B v3 (25 languages, INT8)", | ||
| "default": true, | ||
| "source": "huggingface", | ||
| "repo_id": "streamkit/parakeet-models", | ||
| "revision": "main", | ||
| "files": [ | ||
| "sherpa-onnx-nemo-parakeet-tdt-0.6b-v3-int8.tar.bz2" | ||
| ], | ||
| "expected_size_bytes": 486660829, | ||
| "license": "CC-BY-4.0", | ||
| "license_url": "https://huggingface.co/nvidia/parakeet-tdt-0.6b-v3", | ||
| "sha256": "181f96d0dcac111d68c2ee5843655bb08ecb5fe26f845a915c3e4fca7915b9f8" | ||
| }, | ||
| { | ||
| "id": "silero-vad", | ||
| "name": "Silero VAD (v6.2)", | ||
| "default": true, | ||
| "source": "huggingface", | ||
| "repo_id": "streamkit/parakeet-models", | ||
| "revision": "main", | ||
| "files": [ | ||
| "silero_vad.onnx" | ||
| ], | ||
| "expected_size_bytes": 2327524, | ||
| "license": "MIT", | ||
| "license_url": "https://github.com/snakers4/silero-vad/blob/master/LICENSE", | ||
| "sha256": "1a153a22f4509e292a94e67d6f9b85e8deb25b4988682b7e174c65279d8788e3" | ||
| } | ||
| ] |
There was a problem hiding this comment.
📝 Info: parakeet 0.3.1 changes model packaging and drops CUDA variant relative to 0.3.0
The new parakeet 0.3.1 manifest replaces the 0.3.0 model packaging (separate encoder.int8.onnx/decoder.int8.onnx/joiner.int8.onnx/tokens.txt with file_checksums) with a single sherpa-onnx-nemo-parakeet-tdt-0.6b-v3-int8.tar.bz2 archive plus a top-level sha256, and expected_size_bytes changes accordingly (671145061 -> 486660829). Unlike the other 0.3.0 STT manifests updated in this PR, parakeet 0.3.1 does not include a CUDA variants entry. Both are plausible intentional packaging/release decisions; I could not verify the actual bundle/model contents from the repo, so the correctness of the new checksums/sizes depends on the release artifacts. The two default: true models (main + silero-vad) match the pre-existing pattern in sensevoice/whisper/parakeet-0.3.0 and are not a bug.
Was this helpful? React with 👍 or 👎 to provide feedback.
Automated registry metadata update from run
28751808864.Devin Review
d5ee595