Repository navigation
fix(OMN-20375): advance the receipt-gate pin to omnibase_core#1853 (artifact_sha256) - #350
Conversation
Move the pin of OmniNode-ai/omnibase_core/.github/workflows/receipt-gate.yml in .github/workflows/call-receipt-gate.yml to fad21c40911b356c30f3e38c9075332f11524617, the merge of omnibase_core#1853. That change advances the inner validator checkout ref from d35ae63d3687c13c006015f1d220749bd6fed87c to 50f790aacb515cdc78290a4ff73cb18f2b2cc3e3, whose ModelDodReceipt accepts the artifact_sha256 field. At the old pin, verify / verify rejects every current receipt because they carry artifact_sha256. Same shape as OMN-20132, the tree_sha re-pin. The receipt-gate.yml cross_repo_ref in .github/required-checks.yaml moves to the same sha.
|
Lab: head=f3e4dbd750297d3adc1583f38bee47ae93dd463c host=h201 lane=repin-verify-red-2a21 command="uvx --with pyyaml pytest -q tests/ci/test_sibling_reads_pinned.py tests/ci/test_precommit_ci_backstops_omn19612.py tests/ci/test_precommit_pin_tests_run_in_ci_omn19612.py" observed="45 passed" |
|
OCC autobind rebound this PR's evidence-source stamp line to The receipt gate's own eligibility validator, run against the change-control tree the gate pins for Reported by |
|
Lab: head=6e1e85d90fe2beda5e5e4187cb17c02b37534c81 host=h201 lane=keep3-OMN-20864-dash-4-5d21. Merged dev (aab5c9a) into the branch; the only conflict, call-receipt-gate.yml, already carries the same pin fad21c40911b356c30f3e38c9075332f11524617 on dev, so dev's line was kept. Remaining diff against dev is the receipt-gate cross_repo_ref in .github/required-checks.yaml. Command: uv run --no-project --with pytest --with pyyaml python -m pytest tests/ci/test_sibling_reads_pinned.py tests/ci/test_receipt_gate_pin_artifact_sha256_omn19994.py tests/ci/test_precommit_ci_backstops_omn19612.py -q --noconftest. Observed: 44 passed, exit 0. Hosted CI on this head not yet read. |
Ticket: OMN-20375.
Summary
In OmniNode-ai/omnidash, .github/workflows/call-receipt-gate.yml moves its one reference to OmniNode-ai/omnibase_core/.github/workflows/receipt-gate.yml from @1e69bec909f245be511803191554e5b340def0b7 to @fad21c40911b356c30f3e38c9075332f11524617 and adds a trailing comment citing omnibase_core#1853. The receipt-gate.yml cross_repo_ref in .github/required-checks.yaml moves to the same sha. Same shape as OMN-20132 (the tree_sha re-pin) and the sibling re-pins omnibase_infra#4482, omniclaude#2511 and omnimarket#3265.
Why
omnibase_core#1853 merged as fad21c40911b356c30f3e38c9075332f11524617 on omnibase_core dev. It advances receipt-gate.yml's inner validator checkout ref from d35ae63d3687c13c006015f1d220749bd6fed87c to 50f790aacb515cdc78290a4ff73cb18f2b2cc3e3, so ModelDodReceipt accepts artifact_sha256. Callers pinned by sha at an older commit still run the d35ae63d validator and reject every receipt that carries artifact_sha256.
Verification
tests/ci/test_sibling_reads_pinned.py, test_precommit_ci_backstops_omn19612.py and test_precommit_pin_tests_run_in_ci_omn19612.py pass locally (45 passed). Local pre-commit could not run tsc-typecheck (no node_modules on this host) or normalization-symmetry (no sibling ../omnibase_core checkout); hosted CI runs both. The diff touches only workflow/config YAML; hosted verify / verify on this PR runs the new pin from the PR head (pull_request event), so it proves the pin itself.
Evidence-Ticket: OMN-20375
Evidence-Source: OCC#12369