Repository navigation
fix(OMN-18796): re-pin the advisory-job gate to the dependency-installing reusable - #1709
Merged
Merged
Conversation
…ling reusable The pin that landed in #1708, a956b7d2, ran `python3` against whatever the runner happened to have installed. It passed here, and that is the problem rather than the reassurance: the same commit exited 1 on omninode_infra with `ModuleNotFoundError: No module named 'yaml'` before it read a single workflow file. A verdict that is a property of the runner image can be a confident green as easily as a loud red, and this repository was on the green side of it by accident. omniclaude#2261 (squash d062b74b1e60a3c86ec355d8736fa5d76c903c24) pins the interpreter and the one third-party dependency inside the reusable. This is the re-pin to that commit; nothing else changes, and the gate baseline for this repository is untouched. Onex-Lane: omn18777-advisory-gate-fanout-five-repos-0208
jonahgabriel
enabled auto-merge (squash)
September 19, 2026 06:22
Contributor
|
OCC autobind did not mint a companion for this PR: no changed-file candidate could be proven RED against the merge base, and emitting a PR-existence probe instead would be non-falsifiable evidence (OMN-15247). Hand-authored evidence is required. |
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.
What
OMN-18796, epic OMN-18775. The advisory-job gate caller landed in
omnibase_core#1708pinned toa956b7d2. This re-pins it tod062b74b1e60a3c86ec355d8736fa5d76c903c24, the omniclaude commit where the reusable installs the validator one third-party dependency instead of assuming the runner carries it.Why this is not cosmetic
The old pin ran
python3against whatever the runner happened to have installed. It passed here, and that is the problem rather than the reassurance: the same commit exited 1 on omninode_infra withModuleNotFoundError: No module named 'yaml'before it read a single workflow file, in the same window. A verdict that is a property of the runner image can be a confident green as easily as a loud red, and this repository was on the green side of it by accident.omniclaude#2261pins the interpreter at 3.13 andPyYAML==6.0.2inside the reusable, so the verdict is a property of the validator.Scope
One line. No validator behaviour changes, the census baseline for this repository is untouched, and the enforcement registration from
omnibase_core#1708is unchanged:advisory-job-gate / advisory-job-gateremains inEXPECTED_EXTERNAL_CONTEXTSunder the requiredCI Summaryumbrella, and liverequired_status_checksondevis not written to.Lab-first is not applicable. This is CI tooling with no runtime surface on any lane.
Ticket: OMN-18796
Evidence-Ticket: OMN-18796
Evidence-Source: OCC#10521