Repository navigation
ci(umi): run coordinated checks for v2 changes - #425
Merged
Merged
Conversation
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.
Run the coordinated four-package checks for Language PRs and pushes targeting v2. The shared workflow builds and tests installed wheels on Ubuntu and macOS and runs the OpenPI client profile.
The caller supplies the exact PR head and source repository, including forks. Other peers stay pinned. Both the workflow and Unified source use immutable commit
d445bdb; no secrets are inherited and token access is read-only. Existing Jenkins jobs remain in place for domain and plugin checks.Depends on Unified #21. Validation: actionlint passes; the local required Language selection passes (67 tests). The shared runner has 14 new revision-resolution cases and passed its full local offline suite.
After the caller merges, require the reported
UMI v2 / ...statuses on v2. This PR does not change branch protection or publish packages. Supports brain-score/unified-model-interface#16 and #18.