From 524e5f7c7ef3b6aa760e97acfa0e277f88080bb7 Mon Sep 17 00:00:00 2001 From: Hmbown <101357273+Hmbown@users.noreply.github.com> Date: Wed, 5 Aug 2026 00:42:07 -0700 Subject: [PATCH] docs(verifiers): pin the harness examples to 0.9.4 The README body already said v0.9.4 while the three eval examples still passed --harness.version 0.9.1, which would resolve a two-release-old runtime companion set. --- integrations/verifiers-codewhale/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/integrations/verifiers-codewhale/README.md b/integrations/verifiers-codewhale/README.md index 477a51acf..75ba784b3 100644 --- a/integrations/verifiers-codewhale/README.md +++ b/integrations/verifiers-codewhale/README.md @@ -37,19 +37,19 @@ Then select the package as a Verifiers v1 harness: ```bash uv run eval \ --harness.id codewhale-harness \ - --harness.version 0.9.1 \ + --harness.version 0.9.4 \ --harness.runtime.type docker ``` The default setup downloads all three release runtime companions from the pinned Codewhale tag and verifies each byte against the release checksum -manifest. Before v0.9.1 is published, use an installed candidate for a local +manifest. Before v0.9.4 is published, use an installed candidate for a local subprocess rollout: ```bash uv run eval \ --harness.id codewhale-harness \ - --harness.version 0.9.1 \ + --harness.version 0.9.4 \ --harness.binary-path /absolute/path/to/codewhale \ --harness.runtime.type subprocess ```