ci: run rich transcription regressions in ONNX package checks - #3749
Merged
Merged
Conversation
Signed-off-by: LauraGPT <18321252+LauraGPT@users.noreply.github.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
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
This closes the CI coverage gap after #3747 and #3748: those regressions were verified natively but were not executed by the hosted package workflow.
Validation
git diff --checkpasses.Native validation used Python 3.12. Hosted PR validation passed on Python 3.11 and 3.12; each job log explicitly reports 36 passed, and all existing package checks passed.
Merge Status
Merged as
4a84879ae8ca4d2430953b11c49d609217d93988. The merge tree matches the validated head. Main-branch validation also passed on both Python versions.This changes CI only; it does not publish a package or deploy a website.