Skip to content

release(ci): fix #702 (temperature retry) is unreleased — fleet CI still pins v0.15.0 and every cora-review job fails #708

Closed

Description

@ajianaz

What

Since ~2026-10-27 14:13 WIB every fleet cora review CI job fails with the same engine error:

Error: LLM API returned status 400: {"error":{"code":"invalid_request_error","message":"`temperature` is deprecated for this model.","type":"invalid_request_error","param":null}}

Verified affected today: gaira runs #55/#56, waca runs #155/#156 (2 PRs). Last green cora-review fleet-wide: waca run #154 (13:41 WIB), gaira run #54 (17:58 WIB).

The retry fix already exists: #702 merged 07:17Z today (retry without temperature when the model rejects it). But:

  1. No release carries it — latest release is v0.19.0 (16 Okt).
  2. Fleet CI pins v0.15.0 — even older (gaira ci.yml V=v0.15.0; pinned sha256 install path).
  3. Runner-native fast path: /opt/cora-tool/bin/cora on runner-01 self-reports 0.15.0; the version check short-circuits the download, so bumping the pin alone is not enough — the native copy must be updated (or the cache invalidated).

Why

The merge-gate amendment (2026-08-28) makes a failed review a BLOCKER: every open PR fleet-wide is now unmergeable through the standard gate (gaira: none open now; waca: #189/#190 blocked). This will bite the next PR on any repo the moment it opens.

Requested

Evidence

Activity

  1. ajianaz commented on Oct 27, 2026

    @ajianaz
    CollaboratorAuthor

    RESOLVED 2026-10-27 (CTO):

    1. cora v0.20.0 RELEASED — tag on main HEAD b40b742 (via release: v0.20.0 #710), release body gate passed (CHANGELOG section present, incl. the feat(mcp): cora.scan_prepare needs include/exclude, smarter batch ordering and size hints (agent mode is impractical on large repos) #686 scan_prepare entry), 6 assets + checksums published: https://github.com/codecoradev/cora-code/releases/tag/v0.20.0
    2. gaira CI pin bumped v0.15.0 → v0.20.0 (PR feat(website): landing page redesign — CSS, components, animations #171 merged c7d53aab) — CI run feat: config redesign + severity comparison fix #61 attempt 2 proved the new pin end-to-end: download + checksums + cora review GREEN (first fully-green 5/5 run of the day).
    3. Runner native copy refreshed implicitly — the fast-path version check failed on first run with the new pin and the job downloaded/installed v0.20.0 to /opt/cora-tool/bin/cora (proven by the green cora review in run feat: config redesign + severity comparison fix #61 attempt 2).

    Remaining red cora jobs on other repos (waca #189/#190 etc.): re-run their CI after the same one-line pin bump + checksum update (aarch64 0e65a874…, x86_64 6080dada…); the runner binary is already 0.20.0 so only the pin lines matter for consistency.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions