Repository navigation
chore(OMN-17292): advance omnimarket contract pin to d2b0d9986ed7 - #4677
Closed
onexbot-occ-writer[bot] wants to merge 5 commits into
Closed
onexbot-occ-writer[bot] wants to merge 5 commits into
onexbot-occ-writer[bot] wants to merge 5 commits into
Conversation
Onex-Workflow: Omnimarket contract pin refresh Onex-Run: https://github.com/OmniNode-ai/omnibase_infra/actions/runs/37668615481
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. Considered 13 changed file(s):
This verdict is occ-autobind's, derived from this head and its merge base alone. A second producer, the occ-companion-effect backstop, consumes its own command on the lab bus and may still mint a companion under the generic binding. Whether it does depends on that consumer running, not on this diff (OMN-18876). |
Deleted LEGACY_MIGRATION_TABLE_DECLARATIONS entries for delegation_routing_feedback and delegation_budget_applied_events in src/omnibase_infra/topology/table_grant_derivation.py. Removed both keys from _INTERIM_ENTRIES in tests/ci/test_supplemental_declaration_expiry_omn18863.py. The pinned contract d2b0d9986ed7 now declares these relations via omnimarket#3416 and omnimarket#3436, resolving the test failure. Regenerating against the pin wrote no instances and no catalogs; --check --prove reports PASS=90 FAIL=0 RESIDUAL=0 for prod, stability-test and test.
This was referenced Oct 7, 2026
…es stay retired A new integration test file mirrors the existing board probe results bridge test to verify that delegation_routing_feedback and delegation_budget_applied_events no longer have LEGACY_MIGRATION_TABLE_DECLARATIONS entries. The test confirms the vendored migration file remains in the tree while local, onex-dev, and onex-prod topology instances still declare the relation, satisfying the Integration Test Coverage gate for changes to src/omnibase_infra/topology/table_grant_derivation.py.
jonahgabriel
pushed a commit
to OmniNode-ai/onex_change_control
that referenced
this pull request
Oct 7, 2026
…13210) * evidence(OMN-17292): author OCC companion for OmniNode-ai/omnibase_infra#4677 OCC companion by node_pr_lifecycle_fix_effect (OMN-13317 F1 / OMN-13990 / OMN-14285). Product PR head 9e6af9926b9e027c0bb587166dedd653dbc5d620. * evidence(OMN-17292): self-bind OCC#13210 + rebind contract_sha256 --------- Co-authored-by: omnimarket-bot <bot@omninode.ai>
… the reader surface
Collaborator
|
Superseded by omnibase_infra#4760, the newer PR of the same bot series; closing so it is never landed (drain map 2026-10-09T07:32Z, class superseded-bot). Generated by Claude Code |
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.yamlfromf859c7af5e1d2a4df043bbb5d5e9d873a6c1c495tod2b0d9986ed70f3ddab8b1b7342c935f406abb26, also moves the omnimarket entry of.github/sibling-pins.yamland the inline workflowref:shas that read it (OMN-20331), and 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#13210