Repository navigation
chore(OMN-13131): bump omnibase_core pin to v0.45.0 for renderer-capability runtime - #2771
Merged
Merged
Conversation
…er-capability runtime onex_change_control's [tool.uv.sources] git rev forced omnibase_core 0.44.0 (f325e759) in the combined dev runtime image even though its PyPI constraint (>=0.36.0) already permits 0.45.0. The image staged omnibase_infra + OCC + omnimarket + omnibase_compat together; the differing source revs prevented a single 0.45.0 resolution. Moves the source git rev to the released v0.45.0 tag (dc69b726) so OCC resolves the same omnibase_core as the other image repos. v0.45.0 is additive over 0.44.x; no source changes. - [tool.uv.sources] omnibase-core rev f325e759 (0.44.0) -> dc69b726 (v0.45.0) - uv.lock re-resolved: omnibase-core 0.44.0 -> 0.45.0 Verified: 552 tests passed against core 0.45.0; OCC ModelTicketContract import clean. Evidence-Ticket: OMN-13131
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (11)
📝 WalkthroughWalkthroughTwo new DoD evidence items ( ChangesOMN-13131 Pin-Fix Evidence and Dependency Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~4 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
jonahgabriel
added a commit
that referenced
this pull request
Jun 18, 2026
…fra #2034 + OCC self) Adds two ModelDodReceipt PASS artifacts under drift/dod_receipts/OMN-13131/: - dod-occ-pinfix-self: self-binding receipt carrying OCC PR #2771 so the OCC PR's own occ-preflight eligibility binds on pr_number. - dod-omnibase-infra-pinfix: binds OMN-13131 to omnibase_infra PR #2034 (head c02cc1f70). Both reference the current contract_sha256 (7c4e681b) for contracts/OMN-13131.yaml. Evidence-Ticket: OMN-13131
…fra #2034 + OCC self) Adds two ModelDodReceipt PASS artifacts under drift/dod_receipts/OMN-13131/: - dod-occ-pinfix-self: self-binding receipt carrying OCC PR #2771 so the OCC PR's own occ-preflight eligibility binds on pr_number. - dod-omnibase-infra-pinfix: binds OMN-13131 to omnibase_infra PR #2034 (head c02cc1f70). Both reference the current contract_sha256 (7c4e681b) for contracts/OMN-13131.yaml. Evidence-Ticket: OMN-13131
jonahgabriel
force-pushed
the
jonah/omn-13131-core-pin-045-occ
branch
from
June 18, 2026 21:58
5b1fed2 to
43b744c
Compare
… hashes The OCC merge-eligibility validator iterates dod_evidence items declared in contracts/OMN-13131.yaml and only looks for receipts at those declared paths. Adds the two core-pin-alignment evidence items so the validator discovers the new receipts: - dod-occ-pinfix-self -> OCC PR #2771 (self-binding on pr_number) - dod-omnibase-infra-pinfix -> omnibase_infra PR #2034 (head 6da0f94d1) Adding the items mutates the contract, so re-pins contract_sha256 across all 9 OMN-13131 receipts to the new hash (sha256:5bb534400600da6fb1cbe6a80ec6674f7d62b3a16d69b17cf0df9faf3f52835d), keeping the validator's contract-hash invariant green for the whole set. Local eligibility verified: eligible=True, 9 receipts, hash-bound + PR-bound. Evidence-Ticket: OMN-13131
jonahgabriel
enabled auto-merge
June 18, 2026 22:08
jonahgabriel
added this pull request to the merge queue
Jun 18, 2026
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.
Evidence-Source: 8c1e546
Evidence-Ticket: OMN-13131
Summary
Aligns
onex_change_control'somnibase_coresource pin to the released v0.45.0 so OCC resolves the same core asomnibase_infra/omnimarketin the dev runtime image.The dev runtime image staged
omnibase_infra+onex_change_control+omnimarket+omnibase_compattogether. OCC's[tool.uv.sources]git revf325e759pinnedomnibase_core0.44.0 even though its PyPI constraint>=0.36.0already permits 0.45.0 — the source git rev overrides the constraint at resolution time. The differing source revs across the image repos prevented a single 0.45.0 resolution (omnibase_infra was forced to 0.44.2, missingmodel_renderer_capability_contract-> W5 reducer auto-wiring failed).v0.45.0 is additive over 0.44.x (dashboard renderer-capability contract,
models/runtime_deployment,enums/ui/*,contract_graphIR), so no source changes are required.Changes
[tool.uv.sources]:omnibase-coregitrevf325e759(0.44.0) ->dc69b726248fd0212a3abc0a5a587bd974278739(the v0.45.0 tag). The broad PyPI constraint>=0.36.0is intentionally left as-is (OCC is consumed as a governance library by many repos at varying core versions; no upper bound to relax).uv.lockre-resolved:omnibase-core 0.44.0 (f325e759) -> 0.45.0 (dc69b726)OCC receipts (this PR)
drift/dod_receipts/OMN-13131/dod-occ-pinfix-self/command.yaml— PASS, self-binding (carries this OCC PR number so occ-preflight eligibility binds onpr_number)drift/dod_receipts/OMN-13131/dod-omnibase-infra-pinfix/command.yaml— PASS, binds OMN-13131 to omnibase_infra PR evidence(OMN-12572): bind deploy-agent lane digest PR #2034 (the paired core-pin code PR)Verification (local, against 0.45.0)
uv lock->omnibase-core 0.44.0 -> 0.45.0;uv.lockshowsversion = "0.45.0"ModelTicketContractimports clean against core 0.45.0uv run validate-yaml contracts/OMN-13131.yaml->[OK]No live prod mutation, deploy, or restart.
Summary by CodeRabbit
Dependencies
Chores