From f56e03ad1e98917426f8e8b5217a5e9f06e61e2e Mon Sep 17 00:00:00 2001 From: Omar Nahhas Sanchez Date: Wed, 5 Aug 2026 10:37:03 +0100 Subject: [PATCH] ci: run e2e against upstream A0, not the fork (DEC-082) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The devkit defaults a0_image to ghcr.io/nuevanext/agent-zero:latest-nonroot and this repo never overrode it, so every PR has been proving the plugin works on the private fork while upstream — the only thing anyone actually runs — was verified nowhere. Coverage was aimed at the wrong image. Overridden per repo rather than by changing the devkit default, so the change is scoped to this plugin. If this turns the suite red, that is the point: it means the plugin does not work for the only consumer it has, and the PR e2e is now the place that says so. --- .devkit.yml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/.devkit.yml b/.devkit.yml index e2e240f..43ad064 100644 --- a/.devkit.yml +++ b/.devkit.yml @@ -4,3 +4,11 @@ display_name: DiffVisualizer # e2e_pod_env: # A0_DIFF_VISUALIZER_TEST_PROBE: "1" devkit_major: 2 + +# Test against UPSTREAM A0, not the private fork (DEC-082). +# +# The devkit default is ghcr.io/nuevanext/agent-zero:latest-nonroot, so without +# this line every PR proved the plugin worked on the fork while upstream — the +# only thing anyone actually runs — was verified nowhere. Overriding per repo +# rather than changing the devkit default keeps the blast radius to this plugin. +a0_image: docker.io/agent0ai/agent-zero:latest