Repository navigation
chore(OMN-18010): post-release dev version bump to 0.4.291 - #3367
Merged
onexbot-occ-writer[bot] merged 2 commits intoOct 4, 2026
Merged
onexbot-occ-writer[bot] merged 2 commits into
onexbot-occ-writer[bot] merged 2 commits into
Conversation
Disarms the OMN-16344 release-identity gate that publishing v0.4.290 armed against dev. Triggered-by: https://github.com/OmniNode-ai/omnimarket/actions/runs/37194899264
✅ Architectural Review — PASSEDErrors: 0 What this checks
No architectural violations found. Static architectural lint — no model inference (OMN-14176). |
✅ Hostile Reviewer — PASSEDBlocking findings (critical/error): 0 Gate semantics
Powered by omniintelligence.review_pairing.cli_review — node-based adversarial review via HandlerLlmCliSubprocess (OMN-8524) |
repo-evidence / dod-verify failed on PR omnimarket#3367 head ccba703 with "pull request cites OMN-18010 but carries no contracts/OMN-18010.yaml". This commit adds contracts/OMN-18010.yaml and tests/ci/test_post_release_dev_bump_omn18010.py. The test runs scripts/check_release_identity.py in strict mode (no --base) and asserts exit 0, and asserts uv.lock pins the pyproject.toml version. Locally, node_dod_verify verified the contract at the head (2 passed) and the same test failed at the merge base acd8a5b, where version 0.4.290 equals the reachable tag v0.4.290, so the must-fail control holds.
onexbot-occ-writer
Bot
deleted the
automation/omn-18010-post-release-dev-bump-0.4.291
branch
October 4, 2026 11:41
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 post-release disarm step (OMN-18010, porting OMN-13912). Publishing
v0.4.290left dev's[project].versionequal to the highest published tag, which ARMS the OMN-16344 release-identity gate (scripts/check_release_identity.py) against every subsequent dev PR that touchessrc/**.This PR bumps
[project].versionto0.4.291and re-locksuv.lock, so the gate is disarmed by the same flow that armed it rather than by whichever unrelated PR trips it first.Ticket
OMN-18010 — releases are cut on an explicit trigger; this is the one bump PR that follows a cut, not a per-merge one.
Triggered by
https://github.com/OmniNode-ai/omnimarket/actions/runs/37194899264
Test plan
Evidence-Ticket: OMN-18010
Evidence-Source: OCC#12781