From 3598fb7626a69bf058d18bc6ac59e08030b4f439 Mon Sep 17 00:00:00 2001 From: GitHub CI Date: Thu, 23 Jul 2026 02:26:35 -0700 Subject: [PATCH] chore(deps): protoagent 0.108.0 base + pr-reviewer v0.16.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The base bump is the point of this one: protoAgent#2168 (recipe-declared fan-out width + per-step timings) landed AFTER the v0.107.0 tag, so `max_concurrency: 5` in the review recipe has been inert since v0.12.0 — the five finders kept running as 4+1 under the host's default cap of 4, paying the slowest finder's cost twice. Measured over 60 reviews before the fix: the five-finder recipe's p50 was 458s against 322s for the otherwise-identical four-finder one, which solves to ~136s per finder and ~186s for the sequential synthesize -> verify -> report tail. Expected saving ~136s per structural review, about 30%. It also starts `step_s` / `slowest_step` flowing. Every review so far has recorded them as null, so the split above is an estimate inferred from two recipe populations; after this it is measured. The sequential tail is the larger half and is the next thing worth attacking — but not before the numbers exist. Plugin v0.14.1 -> v0.16.0 brings: v0.14.2 grounding no longer mistakes prose for a code quote (it downgraded a TRUE finding on projectBoard-plugin#94 within an hour of deploying) v0.15.0 `@vera review` — on-demand panel, admin-gated, server-side permission v0.16.0 every guard reports its DECISION, not only when it fires; and a finding with `line: 0` no longer silently blocks convergence forever Co-Authored-By: Claude Opus 4.8 (1M context) --- Dockerfile | 4 ++-- protoagent.bundle.yaml | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/Dockerfile b/Dockerfile index 8322871..9321923 100644 --- a/Dockerfile +++ b/Dockerfile @@ -9,7 +9,7 @@ # protoAgent core forward on the same image roll — core and member bumps are # decoupled. Bump this deliberately (and re-verify), keeping it in step with the # manifest's `verified_against`. Tag format is bare semver (no `v` prefix). -FROM ghcr.io/protolabsai/protoagent:0.106.0 +FROM ghcr.io/protolabsai/protoagent:0.108.0 USER root @@ -31,7 +31,7 @@ ARG GITHUB_PLUGIN_REF=v0.3.0 RUN git clone --depth 1 --branch "${GITHUB_PLUGIN_REF}" \ https://github.com/protoLabsAI/github-plugin.git /opt/protoagent/plugins/github \ && rm -rf /opt/protoagent/plugins/github/.git -ARG PR_REVIEWER_PLUGIN_REF=v0.14.1 +ARG PR_REVIEWER_PLUGIN_REF=v0.16.0 RUN git clone --depth 1 --branch "${PR_REVIEWER_PLUGIN_REF}" \ https://github.com/protoLabsAI/pr-reviewer-plugin.git /opt/protoagent/plugins/pr-reviewer \ && rm -rf /opt/protoagent/plugins/pr-reviewer/.git diff --git a/protoagent.bundle.yaml b/protoagent.bundle.yaml index c9d6514..8ab513d 100644 --- a/protoagent.bundle.yaml +++ b/protoagent.bundle.yaml @@ -25,12 +25,12 @@ description: >- own work; never posts a blocking verdict against pending CI. # The core version this pin set was last verified against (ADR 0049 rule 2). -verified_against: 0.106.0 +verified_against: 0.108.0 plugins: - { id: workflows, builtin: true } # the recipe engine (code-review panels run through it) - { id: github, url: https://github.com/protoLabsAI/github-plugin, ref: v0.3.0 } - - { id: pr-reviewer, url: https://github.com/protoLabsAI/pr-reviewer-plugin, ref: v0.14.1 } + - { id: pr-reviewer, url: https://github.com/protoLabsAI/pr-reviewer-plugin, ref: v0.16.0 } enabled: [workflows, github, pr-reviewer] # suggested turn-on list (applied to plugins.enabled)