Skip to content

v3.0.1 — fixes before the announcement

Latest

Choose a tag to compare

@cirolini cirolini released this 21 Sep 12:32
0b32576

A fix release. Nothing new to configure; every input keeps its meaning. If you pin @v3, you get this automatically.

The summary no longer forgets what it did not review. The last reviewed commit advanced even when files were skipped as too large, the diff was truncated, or the model's output was unusable — so on the next push those files were neither reviewed nor listed under "Not reviewed". It now advances only after a complete run, and the summary says when the next push will review an earlier range again. Findings from a review GitHub rejected are no longer counted as posted: they are listed in the summary and retried.

Incremental review survives a merge from the base branch or a rebase. Both used to put changes from outside the pull request into the diff, and GitHub rejected the whole review with a 422. The comparison is checked first and falls back to reviewing the whole pull request, saying why.

One-click suggestions only where they apply. A finding moved a few lines to fit the diff now shows its suggestion as a plain code block, so "Commit suggestion" cannot overwrite code it was not written for.

Security: .genai-review.yml is read from the base branch. It was read from disk: with a checkout, the pull request controlled it — ignore_paths: ["**"] could review a change out of existence, and base_url could send the API key elsewhere. Without a checkout, as recommended, it was never read at all. It is now fetched over the API from the base commit, and base_url is an action input only. If you set base_url in .genai-review.yml, move it to the workflow.

The default max_tokens is 8192 (was 2048). At 2048 a review of a large pull request truncated mid-JSON and was lost entirely.

Also: the action is now named "GenAI Code Review" in action.yml, and the docs no longer claim @v2 was untouched — it points at the fix-only v2.1.

Full list in the changelog.