chore(deps): bump omnibase-core to 0.47.10 (OMN-18075) by onexbot-occ-writer[bot] · Pull Request #3437 · OmniNode-ai/omnibase_infra

onexbot-occ-writer · 2026-09-11T19:50:50Z

Summary

Automated dependency bump triggered by a new release of omnibase_core (0.47.10).

Updates uv.lock via uv lock --upgrade-package omnibase_core
Updates pyproject.toml exact pin (==X.Y.Z) to match, when this repo pins that exactly
No other source code changes

Cascade provenance (OMN-16286)

This PR carries no dedicated testing of its own beyond this repo's own
CI running against the new lockfile. Its cited evidence below is the
upstream release's own Evidence-Ticket/Evidence-Source pair, which
already proved the released package version -- reused honestly rather
than fabricated or exempted:

Source repo: OmniNode-ai/omnibase_core
Released version: 0.47.10

Triggered by

Release workflow: https://github.com/OmniNode-ai/omnibase_core/actions/runs/34639831299

Test plan

CI passes (lockfile resolution is valid)
Downstream tests pass with the new dependency version

Evidence-Ticket: OMN-18075
Evidence-Source: OCC#9122

Automated dependency cascade from OmniNode-ai/omnibase_core release 0.47.10. Triggered-by: https://github.com/OmniNode-ai/omnibase_core/actions/runs/34639831299

onexbot-occ-writer · 2026-09-11T19:51:11Z

No OCC evidence companion was minted for this PR.

this PR is already bound to OCC#9094; its evidence companion exists and nothing needs authoring

To clear this: Nothing to do — the companion already exists.

Reported by node_occ_companion_effect (decline code already_bound, OMN-16665). This decision was made against the PR's LIVE state at compute time, not at publish time — a green publisher job only means the command reached the broker.

onexbot-occ-writer · 2026-09-11T19:51:33Z

OCC autobind did not rebind this PR.

This PR's evidence-source stamp line names OCC#9094, which is merged. A second companion, OCC#9122, was minted for this PR, but a merged companion is settled evidence — the merged-companion gate may already have passed against it — so the stamp was left pointing at OCC#9094 and nothing was written.

To clear this: OCC#9122 is redundant and can be closed. If the binding really should move, change the stamp by hand.

Reported by occ_companion_emitter (OMN-18089).

…fra#3437 OCC companion by node_pr_lifecycle_fix_effect (OMN-13317 F1 / OMN-13990 / OMN-14285). Product PR head dded487ffa400e3efb9ba2b3c41a2bbcd11da8ab.

…ibase_infra#3437 (#9122) * evidence(OMN-18075): author OCC companion for OmniNode-ai/omnibase_infra#3437 OCC companion by node_pr_lifecycle_fix_effect (OMN-13317 F1 / OMN-13990 / OMN-14285). Product PR head dded487ffa400e3efb9ba2b3c41a2bbcd11da8ab. * evidence(OMN-18075): self-bind OCC#9122 + rebind contract_sha256 --------- Co-authored-by: omnimarket-bot <bot@omninode.ai>

…se-core-0.47.10-omn-18075

….47.10 bump The runner image identity digest binds pyproject.toml and uv.lock as version components, so a dependency bump necessarily changes it. The cascade updated the lockfile without regenerating the binding, leaving the recorded digest stale and failing tests/ci/test_runner_image_identity.py and the runner image smoke job. Regenerated with scripts/ci/runner_image_identity.py --mode generate, the command the failing assertion itself names; verify mode now exits 0. The values match what CI computed exactly: identity 9d792733f04ae323f11610aefdffd328, shared env e5b91f9191f06a0d66dcf5cf. Focused suite: 11 passed. CI's own red is the negative control. This commit also merges dev, which the branch was behind, picking up a vendored node migration whose absence failed the vendor sync hook.

…the seam pin Two more places record the pinned core version, and the cascade updates neither. Both failures named their own remedy and neither is an API break. - tests/unit/runtime/test_fallback_matrix_sync.py asked for scripts/update_version_matrix.py, which rewrote the fallback matrix to omnibase_core >=0.47.10,<0.48.0. - tests/unit/runtime/test_seam_released_core_pin.py froze core_version 0.47.9 in the core_release seam fixture; bumped to 0.47.10. Prior cascade PRs #3369 and #3359 updated this same fixture, so this follows the established precedent. Focused suite over the three affected files: 15 passed. CI's reds are the negative control.

…ibase_infra#3437 (#9122) * evidence(OMN-18075): author OCC companion for OmniNode-ai/omnibase_infra#3437 OCC companion by node_pr_lifecycle_fix_effect (OMN-13317 F1 / OMN-13990 / OMN-14285). Product PR head dded487ffa400e3efb9ba2b3c41a2bbcd11da8ab. * evidence(OMN-18075): self-bind OCC#9122 + rebind contract_sha256 --------- Co-authored-by: omnimarket-bot <bot@omninode.ai>

* chore(deps): bump omnibase_core to 0.47.10 Automated dependency cascade from OmniNode-ai/omnibase_core release 0.47.10. Triggered-by: https://github.com/OmniNode-ai/omnibase_core/actions/runs/34639831299 * chore(OMN-18075): regenerate the runner image identity lock for the 0.47.10 bump The runner image identity digest binds pyproject.toml and uv.lock as version components, so a dependency bump necessarily changes it. The cascade updated the lockfile without regenerating the binding, leaving the recorded digest stale and failing tests/ci/test_runner_image_identity.py and the runner image smoke job. Regenerated with scripts/ci/runner_image_identity.py --mode generate, the command the failing assertion itself names; verify mode now exits 0. The values match what CI computed exactly: identity 9d792733f04ae323f11610aefdffd328, shared env e5b91f9191f06a0d66dcf5cf. Focused suite: 11 passed. CI's own red is the negative control. This commit also merges dev, which the branch was behind, picking up a vendored node migration whose absence failed the vendor sync hook. * chore(OMN-18075): carry the 0.47.10 bump into the version matrix and the seam pin Two more places record the pinned core version, and the cascade updates neither. Both failures named their own remedy and neither is an API break. - tests/unit/runtime/test_fallback_matrix_sync.py asked for scripts/update_version_matrix.py, which rewrote the fallback matrix to omnibase_core >=0.47.10,<0.48.0. - tests/unit/runtime/test_seam_released_core_pin.py froze core_version 0.47.9 in the core_release seam fixture; bumped to 0.47.10. Prior cascade PRs #3369 and #3359 updated this same fixture, so this follows the established precedent. Focused suite over the three affected files: 15 passed. CI's reds are the negative control. --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: jonahgabriel <jonah@omninode.ai>

chore(deps): bump omnibase_core to 0.47.10

dded487

Automated dependency cascade from OmniNode-ai/omnibase_core release 0.47.10. Triggered-by: https://github.com/OmniNode-ai/omnibase_core/actions/runs/34639831299

onexbot-occ-writer Bot mentioned this pull request Sep 11, 2026

evidence(OMN-18075): OCC Evidence-Source autobind for OmniNode-ai/omnibase_infra#3437 OmniNode-ai/onex_change_control#9122

Merged

jonahgabriel enabled auto-merge (squash) September 11, 2026 20:57

jonahgabriel added 3 commits September 11, 2026 19:23

Merge remote-tracking branch 'origin/dev' into automation/bump-omniba…

5c1d29a

…se-core-0.47.10-omn-18075

jonahgabriel merged commit fccef30 into dev Sep 12, 2026
136 checks passed

jonahgabriel deleted the automation/bump-omnibase-core-0.47.10-omn-18075 branch September 12, 2026 00:06

jonahgabriel mentioned this pull request Sep 12, 2026

chore(OMN-18202): bump omnibase-core pin to 0.47.12 and carry the three version-bookkeeping surfaces #3448

Merged

2 of 3 tasks

Navigation Menu

Repository navigation

chore(deps): bump omnibase-core to 0.47.10 (OMN-18075) - #3437

chore(deps): bump omnibase-core to 0.47.10 (OMN-18075)#3437
jonahgabriel merged 4 commits into
devfrom
automation/bump-omnibase-core-0.47.10-omn-18075

onexbot-occ-writer Bot commented Sep 11, 2026 •

edited by jonahgabriel

Loading

Uh oh!

onexbot-occ-writer Bot commented Sep 11, 2026

Uh oh!

onexbot-occ-writer Bot commented Sep 11, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

onexbot-occ-writer Bot commented Sep 11, 2026 • edited by jonahgabriel Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Cascade provenance (OMN-16286)

Triggered by

Test plan

Uh oh!

onexbot-occ-writer Bot commented Sep 11, 2026

Uh oh!

onexbot-occ-writer Bot commented Sep 11, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

onexbot-occ-writer Bot commented Sep 11, 2026 •

edited by jonahgabriel

Loading