v1.2.0

On pull requests, the action lists every finding in one comment and updates it on each run: GitHub shows at most 10 error and 10 warning annotations per step. The comment gives the gate's result, the run's API requests, input tokens and cost, and the findings by level and file, linked to their lines, with JevGate 0.26.0's mark on each finding that fails the gate and, from 0.28.0, how often findings like it were right (from 0.30.0, in a preview language, how often in that language); a run that could not finish (no key, HTTP 402, the request budget) opens with a caution and the reasons. It needs pull-requests: write; where the token can't comment, as on pull requests from forks, the run says so and carries on. comment: false turns it off.

New input api-key-kind (typesafe, openrouter or vercel) takes OpenRouter and Vercel AI Gateway keys; the gateways need JevGate 0.26.0 or later.

The action removes an answer cache a pull request commits under .jevgate/cache before restoring its own, as such answers could clear the pull request's own code; JevGate 0.28.0 and later also ignore cache files Git tracks.

Fixes: exit-code is set when the base revision is missing, and the report output is a Windows path on Windows runners.

@v1 now points here.

v1.1.0

New input sarif-file: also writes the findings as SARIF for GitHub code scanning, replayed from the answers the check just cached, so it costs nothing. Needs JevGate 0.18.0 or later. @v1 now points here.

v1.0.1

The action is named JevGate Code Review, so it can be listed on the GitHub Marketplace. Behavior is unchanged; @v1 now points here.

v1.0.0

First release. Use it as Tech-Byte-Frontier/jevgate-action@v1; see the README for inputs. Requires JevGate 0.17.0 or later, the first version with release binaries.