Tech-Byte-Frontier · tauanbinato · Sep 28, 2026 · Sep 28, 2026
diff --git a/CHANGELOG.md b/CHANGELOG.md
diff --git a/Cargo.lock b/Cargo.lock
diff --git a/Cargo.toml b/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "jevgate"
-version = "0.25.0"
+version = "0.30.0"
 edition = "2024"
 rust-version = "1.90"
 description = "Code-review gate for CI and coding agents: asks TypeSafe Jev small questions about functions, files, tests and docs, and reports maintainability, test, security and documentation findings with locations and how often findings like them were right"

diff --git a/README.md b/README.md
@@ -74,7 +74,7 @@ jobs:
       - uses: Tech-Byte-Frontier/jevgate-action@v1
         with:
           api-key: ${{ secrets.TYPESAFE_API_KEY }}
-          version: 0.25.0
+          version: 0.30.0
 ```
 
 It reviews only what the pull request changed (the functions, tests and comments on changed lines, and copies where either copy changed), annotates each finding on its line and writes a job summary; unchanged code is answered from the cache for free. [Continuous integration](https://tech-byte-frontier.github.io/jevgate/ci.html) covers pre-commit, other CI systems, pull requests from forks, budgets and a gate policy the change cannot edit.

diff --git a/npm/package.json b/npm/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@tech-byte-frontier/jevgate",
-  "version": "0.25.0",
+  "version": "0.30.0",
   "description": "JevGate, the code-review gate for CI and coding agents: this package downloads the matching release binary, checks its SHA-256, caches it and runs it",
   "keywords": [
     "code-review",

diff --git a/plugin/.claude-plugin/plugin.json b/plugin/.claude-plugin/plugin.json
@@ -1,7 +1,7 @@
 {
   "name": "jevgate",
   "displayName": "JevGate",
-  "version": "0.25.0",
+  "version": "0.30.0",
   "description": "JevGate in the agent's loop: checks each edit and the end of each turn, keeps Claude working while findings fail the gate, and adds JevGate's MCP tools and a skill for acting on findings. Runs the jevgate command, 0.27 or later, which you install separately.",
   "author": {
     "name": "Tech Byte Frontier",

diff --git a/site/src/ci.md b/site/src/ci.md
@@ -17,7 +17,7 @@ jobs:
       - uses: Tech-Byte-Frontier/jevgate-action@v1
         with:
           api-key: ${{ secrets.TYPESAFE_API_KEY }}
-          version: 0.25.0
+          version: 0.30.0
 ```
 
 The action installs a checked release binary, keeps `.jevgate/cache` in the Actions cache and runs `jevgate check --base <pull request base> --format github`; `args` passes more flags, such as `--rule default --rule security` to add the security rules to the default ones. Naming a rule replaces the selection, and a selection without a mature rule level never fails the default gate: `--rule security` alone reports security findings without ever failing the gate. It runs on Linux, macOS and Windows runners. For an OpenRouter or Vercel AI Gateway key, leave `api-key` out and set the key's variable in the step's `env`, such as `OPENROUTER_API_KEY: ${{ secrets.OPENROUTER_API_KEY }}`, with `version` 0.26.0 or later; jevgate-action 1.2 adds `api-key-kind: openrouter` or `api-key-kind: vercel` for the same.
@@ -66,7 +66,7 @@ Before each commit, with [pre-commit](https://pre-commit.com), review what is st
 ```yaml
 repos:
   - repo: https://github.com/Tech-Byte-Frontier/jevgate
-    rev: v0.25.0
+    rev: v0.30.0
     hooks:
       - id: jevgate-system   # the jevgate on PATH; `jevgate` builds it with Rust instead
 ```