ci: weekly check for new Kokoro model releases#24
Merged
Conversation
Adds a workflow that watches thewh1teagle/kokoro-onnx for new `model-files-v*` releases. When the upstream tag is ahead of what's pinned in stackvox/engine.py, opens a single labelled `model-upgrade` issue with a maintainer checklist (URL bump, filename check, voice roster diff, sample-rate sanity, smoke test). Schedule: 09:00 UTC every Monday + workflow_dispatch. Deliberately opens an issue, not a PR. Model upgrades can change the ONNX schema, sample rate, or voice roster — a blind URL bump could ship broken audio. Maintainer evaluates manually. Idempotent: skips creation when a model-upgrade issue is already open, so the weekly run won't pile up duplicates. Notes: - kokoro-onnx publishes both Python-package (`v*`) and model-file (`model-files-v*`) releases. The action filters for the latter so package releases don't trigger false positives. - The version regex matches multiple identical hits in engine.py (one for the model URL, one for the voices URL) and de-dupes; if the two URLs ever drift to different tags, the workflow fails fast and a maintainer notices. - Pinned actions to SHAs per StackOne security policy. `gh` CLI is pre-installed on Ubuntu runners, no SHA needed. Heads-up: upstream is currently at model-files-v1.1, stackvox is pinned to model-files-v1.0 — the first run of this workflow will open a real upgrade issue. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3 tasks
StuBehan
added a commit
that referenced
this pull request
Apr 30, 2026
…26) The original tag-name-only filter shipped in #24 would have flagged `model-files-v1.1` as an upgrade candidate even though that release ships only a Mandarin variant (`kokoro-v1.1-zh.onnx` / `voices-v1.1-zh.bin`). Bumping engine.py URLs to it would silently swap the multilingual model for a Chinese-focused one. Tightens the jq filter to require both `kokoro-vX.Y.onnx` and `voices-vX.Y.bin` assets to be present in the release before treating it as a successor. With this in place the workflow currently resolves `model-files-v1.0` (== pinned) and reports up-to-date, as it should. A future general release (with non-suffixed asset names) will surface correctly. This was meant to land as a follow-up commit on #24 but the squash merge captured only the first commit on that branch. Filing as its own PR. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
Adds `.github/workflows/check-kokoro-model.yml` — a weekly job that watches `thewh1teagle/kokoro-onnx` for new `model-files-v*` releases. When the upstream tag is ahead of what's pinned in `stackvox/engine.py`, it opens a single labelled `model-upgrade` issue with a maintainer checklist.
Why an issue, not a PR
Model upgrades can change:
A blind URL bump could ship broken audio. A maintainer needs to evaluate manually before bumping.
Behaviour
Heads-up
stackvox is currently pinned to `model-files-v1.0`. Upstream has `model-files-v1.1` already published. The first run of this workflow will open a real upgrade issue — that's expected, not a bug. Treat it as the first natural test of the pipeline.
Test plan