Repository navigation
chore(OMN-17292): advance omnimarket contract pin to 7112b8e82ac6 - #4078
Merged
Merged
Conversation
Onex-Workflow: Omnimarket contract pin refresh Onex-Run: https://github.com/OmniNode-ai/omnibase_infra/actions/runs/36042349265
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 24, 2026
#11129) * evidence: OCC companion pass 1 for OmniNode-ai/omnibase_infra#4078 * evidence: OCC companion self-bind for #11129 --------- Co-authored-by: node-occ-companion-effect <occ-companion-effect@omninode.ai>
Patel230
added a commit
that referenced
this pull request
Sep 25, 2026
Conflict in .github/omnimarket-contract-pin.yaml: dev's refresh bot advanced the pin to 7112b8e8 (#4078); this branch pins 3441453c, omnimarket#2847's merge, which contains 7112b8e8. Kept 3441453c, the forward pin. After the merge: grant derivation --check --prove in sync on 3 instances, every rendered catalog passes --check, tenant GUC parity 0 violations; tests/unit/topology, tests/unit/validation, tests/ci: 6880 passed, 17 failed, all 17 also failing on untouched dev.
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.
Automated omnimarket contract-pin advance (OMN-17292).
Advances
.github/omnimarket-contract-pin.yamlfrom923b76baef5c013cefb79989f3f7d6626a2ad18cto7112b8e82ac605e0c62d666bc32f3d4a04ef3a70and 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#11129