Skip to content

πŸ”΄ Release branch not green: release/v3.8.51Β #13866

Description

@github-actions

The release-green validation found HARD failures on release/v3.8.51.
These are real defects that would block the release PR β€” fix them in the
originating PR branch (via co-authorship), not by demanding it from contributors.

Run: https://github.com/diegosouzapw/OmniRoute/actions/runs/35090039592 (mode: push)

Offending push range (b4f51b2e9..0cc016936):

0cc016936067 fix(db): give conversation_turn_nodes its own 1-day retention (#13344)
──────── verdict ────────
HARD failures (block β€” real defects): 1
  ❌ Docs sync + fabricated-docs (strict): βœ— In code but missing from .env.example: 1
Ratchet drift (non-blocking β€” rebaseline at release): 1
  🟑 File-size ratchet: βœ— open-sse/executors/codex.ts: 1529 > congelado 1528 (nΓ£o pode crescer)

❌ NOT release-green β€” hard failures must be fixed (in the originating PR branch, via co-authorship).

Ratchet drift (eslint warnings / cognitive-complexity / file-size) listed above is expected mid-cycle and is rebaselined at release β€” it is NOT a contributor concern and did not, on its own, open this issue.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    base-redRelease/main tip is red β€” PRs cut now inherit these failuresbugSomething isn't workingkeep-openOngoing community thread β€” exclude from stale auto-close

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions