Repository navigation
chore(deps): bump omnibase-core to 0.47.7 (OMN-15660) - #3369
Merged
Merged
Conversation
Automated dependency cascade from OmniNode-ai/omnibase_core release 0.47.7. Triggered-by: https://github.com/OmniNode-ai/omnibase_core/actions/runs/34397414560
Contributor
Author
|
No OCC evidence companion was minted for this PR. this PR is already bound to OCC#8804; its evidence companion exists and nothing needs authoring To clear this: Nothing to do — the companion already exists. Reported by |
…0.47.7 bump The runner image identity binding folds pyproject.toml and uv.lock into its shared_env_digest (scripts/ci/runner_image_identity.py MANIFEST_INPUTS), so the 0.47.7 dependency bump invalidates the recorded lock. runner-image-build-smoke failed closed on the drift: runner image shared_env_digest is stale (recorded='b7668bc41f7b52e60cb94fe7', recomputed='f5af1a6e4eeb41cb1e22650f') Regenerated with 'scripts/ci/runner_image_identity.py --mode generate'; the recomputed shared_env_digest reproduces the value CI derived independently. image_version is unchanged at 7 - the binding moved because its inputs moved, not because the image was rebuilt. The dependency cascade does not regenerate this lock, which is why a bump PR lands red here every time.
…ck bump moves Same three-surface follow-up the 0.47.6 bump took in #3359 (cbac0e4) and the 0.47.4 bump in #3242. The dependency cascade moves pyproject.toml + uv.lock and stops; three surfaces in this repo assert a recorded value against a live recompute and go red until each is advanced by its own generator. - src/omnibase_infra/runtime/version_compatibility.py — _FALLBACK_MATRIX regenerated by scripts/update_version_matrix.py, the generator the drift test names in its own failure message. omnibase_core >=0.47.7,<0.48.0. - tests/fixtures/seams/core_release/0.46.11_expected_symbols.json — core_version 0.47.6 -> 0.47.7 by the fixture's documented procedure, header comment moved with the field. No symbol or typed_field row moved, so the frozen OMN-14628 seam already holds on 0.47.7 — the pin advanced, the assertion did not weaken. - docker/runners/runner-image.lock.json — in the preceding commit. RED before, on the governed pre-push full-suite escalation at 5f6fb45: test_fallback_matrix_sync.py::TestFallbackMatrixSync::test_update_version_matrix_check_passes and test_seam_released_core_pin.py::test_seam_released_core_pin_importable_and_typed ("omnibase_core.__version__='0.47.7' but fixture freezes '0.47.6'"). GREEN after, locally: 15 passed across test_fallback_matrix_sync.py, test_seam_released_core_pin.py and tests/ci/test_runner_image_identity.py.
jonahgabriel
pushed a commit
to OmniNode-ai/onex_change_control
that referenced
this pull request
Sep 9, 2026
…ibase_infra#3369 (#8831) * evidence(OMN-15660): author OCC companion for OmniNode-ai/omnibase_infra#3369 OCC companion by node_pr_lifecycle_fix_effect (OMN-13317 F1 / OMN-13990 / OMN-14285). Product PR head 68bd21f8235b7ea329893be284d58c726ecd6f6e. * evidence(OMN-15660): self-bind OCC#8831 + rebind contract_sha256 --------- Co-authored-by: omnimarket-bot <bot@omninode.ai>
jonahgabriel
deleted the
automation/bump-omnibase-core-0.47.7-omn-15660
branch
September 9, 2026 21:27
jonahgabriel
added a commit
that referenced
this pull request
Sep 11, 2026
…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.
jonahgabriel
added a commit
that referenced
this pull request
Sep 12, 2026
* 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>
Patel230
pushed a commit
that referenced
this pull request
Sep 16, 2026
* 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>
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.
Summary
Automated dependency bump triggered by a new release of
omnibase_core(0.47.7).uv.lockviauv lock --upgrade-package omnibase_corepyproject.tomlexact pin (==X.Y.Z) to match, when this repo pins that exactlyCascade 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:
OmniNode-ai/omnibase_core0.47.7Triggered by
Release workflow: https://github.com/OmniNode-ai/omnibase_core/actions/runs/34397414560
Test plan
Evidence-Ticket: OMN-15660
Evidence-Source: OCC#8831