[jonahgabriel]

Problem (verified live 2026-07-03 ~17:30Z on core PR #1381)

validate fails on omnibase_core dev PRs with the OMN-13411 release-identity gate:

FAIL: packaged source changed but pyproject version 0.46.4 is NOT ahead of the latest published version 0.46.4 (OMN-13411 release-identity gate).

Since the 0.46.4 release train published earlier today, dev has accumulated packaged-source changes while project.version still reads 0.46.4 — so the gate fires on every PR to dev regardless of the PR's own content (the triggering PR, OMN-13875's #1381/#1383, touches only workflow YAML). This wedges all core dev work, including the in-flight OMN-13888 validator-redesign lane and OMN-13875/OMN-13911.

Fix

Bump project.version 0.46.4 → 0.46.5 (the gate's own prescribed remedy) + regenerate uv.lock (embeds the self-version at [[package]] name = "omnibase-core"). No PyPI publish action here — 0.46.5 publishes on the next release train. Covered by the standing releases-autonomous grant (bump-to-unblock).

Verification

• python3 scripts/check_release_identity.py → OK: version 0.46.5 is ahead of latest published 0.46.4.
• uv run pytest tests/scripts/test_check_release_identity.py -v → 9/9 passed, including the previously-failing test_live_invocation_smoke.
• uv run pre-commit run --files pyproject.toml uv.lock → all applicable hooks Passed, including "No code merged onto a published version without a bump (OMN-13411)".
• Targeted verification per the accepted OMN-13875 precedent (workflow/config-only diffs get targeted proof, not a full multi-hour local suite) — this diff touches zero source files, only version metadata.

DoD

• Bump PR merged to dev; validate (release-identity) green.
• Evidence commented on OMN-13910.
• omnibase_core#1383 (OMN-13911) rebased once this merges.

Evidence-Ticket: OMN-13910

Evidence-Source: OCC#3550

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 57 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: fe867c44-51e5-412f-838e-8fefa123660e

📥 Commits

Reviewing files that changed from the base of the PR and between 6e2edf7 and 8de5398.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• pyproject.toml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jonah/omn-13910-release-identity-bump

---

_{Comment @coderabbitai help to get the list of available commands.}

[jonahgabriel]

Reopening to force a fresh occ-preflight run now that Evidence-Source: OCC#3550 is in the body.