Repository navigation
chore(OMN-17292): advance omnimarket contract pin to 3038d1dabade - #3594
Merged
Merged
Conversation
Contributor
Author
|
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. |
jonahgabriel
pushed a commit
to OmniNode-ai/onex_change_control
that referenced
this pull request
Sep 15, 2026
#9707) * evidence: OCC companion pass 1 for OmniNode-ai/omnibase_infra#3594 * evidence: OCC companion self-bind for #9707 --------- Co-authored-by: node-occ-companion-effect <occ-companion-effect@omninode.ai>
Patel230
pushed a commit
that referenced
this pull request
Sep 16, 2026
…t] (#3594) Co-authored-by: omninode-bot <bot@omninode.ai>
Patel230
pushed a commit
to OmniNode-ai/onex_change_control
that referenced
this pull request
Sep 16, 2026
#9707) * evidence: OCC companion pass 1 for OmniNode-ai/omnibase_infra#3594 * evidence: OCC companion self-bind for #9707 --------- Co-authored-by: node-occ-companion-effect <occ-companion-effect@omninode.ai>
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.
Automated omnimarket contract-pin advance (OMN-17292).
Advances
.github/omnimarket-contract-pin.yamlfromfa7f0d26f37a638f3985c1b19c43728a118a7dbato3038d1dabadea4973707f0228862b4aef4e09242and regenerates the derived application-database TABLE grants and rendered catalogs in the same commit.This PR is the surface upstream contract drift is supposed to land on. Before OMN-17292 this same drift appeared as a red required check on every open omnibase_infra PR simultaneously, with no action available to their authors (OMN-17141, OMN-16930, OMN-17290).
The advance was proven forward-only against real omnimarket history (
scripts/ci/check_omnimarket_contract_pin_advance.py), so it cannot silently revert grants the way the stale pin in OMN-15701 did, and the regenerated output already passes--check --provelocally in the bot run.Evidence-Ticket: OMN-17292
Evidence-Source: OCC#9707