Repository navigation
chore(OMN-18010): post-release dev version bump to 0.4.91 [release-on-merge] - #2558
Merged
onexbot-occ-writer[bot] merged 1 commit intoSep 15, 2026
Conversation
Disarms the OMN-16344 release-identity gate that publishing v0.4.90 armed against dev. Triggered-by: https://github.com/OmniNode-ai/omnimarket/actions/runs/34908446793
✅ Architectural Review — PASSEDErrors: 0 What this checks
No architectural violations found. Static architectural lint — no model inference (OMN-14176). |
Contributor
Author
|
OCC autobind did not mint a companion for this PR: no changed-file candidate could be proven RED against the merge base, and emitting a PR-existence probe instead would be non-falsifiable evidence (OMN-15247). Hand-authored evidence is required. |
✅ Hostile Reviewer — PASSEDBlocking findings (critical/error): 0 Gate semantics
Powered by omniintelligence.review_pairing.cli_review — node-based adversarial review via HandlerLlmCliSubprocess (OMN-8524) |
This was referenced Sep 15, 2026
jonahgabriel
pushed a commit
to OmniNode-ai/onex_change_control
that referenced
this pull request
Sep 15, 2026
…9599) * evidence: OCC companion pass 1 for OmniNode-ai/omnimarket#2558 * evidence: OCC companion self-bind for #9599 --------- Co-authored-by: node-occ-companion-effect <occ-companion-effect@omninode.ai>
onexbot-occ-writer
Bot
deleted the
automation/omn-18010-post-release-dev-bump-0.4.91
branch
September 15, 2026 02:53
Patel230
pushed a commit
to OmniNode-ai/onex_change_control
that referenced
this pull request
Sep 16, 2026
…9599) * evidence: OCC companion pass 1 for OmniNode-ai/omnimarket#2558 * evidence: OCC companion self-bind for #9599 --------- Co-authored-by: node-occ-companion-effect <occ-companion-effect@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
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.90left 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.91and re-locksuv.lock, so the gate is disarmed by the same flow that armed it rather than by whichever unrelated PR trips it first.The title carries the release-on-merge marker on purpose: this commit touches
pyproject.toml, so without the marker its own merge would re-enter the release workflow and publish an empty version.Ticket
OMN-18010 — release on merge for every publishing repo.
Triggered by
https://github.com/OmniNode-ai/omnimarket/actions/runs/34908446793
Test plan
Evidence-Ticket: OMN-18010
Evidence-Source: OCC#9599