HarnessRouter Community Edition: the self-hosted, Apache-2.0 edition of the unified interface for agent harnesses. Run Codex, Claude Code, Hermes, PI, DSH, and more through one API, with sessions, streaming, files, cancellation, and failure handling. Implements the Unified Harness Protocol (UHP), an open standard. Your keys, your infrastructure.
Python agent-apiagent-frameworkagent-harnessai-agentsai-infrastructurecoding-agentconformance-testingdeepseek-harnessharness-engineeringhermesllmopen-protocolopen-sourceopen-standardpi-coding-agentself-hosteduhpunified-apiunified-harness-protocolunified-interface
ops(hub-cleanup): the token scope a delete needs (#142)
github-actions[bot]48ab9aebf9b5
diff --git a/.github/workflows/hub-cleanup.yml b/.github/workflows/hub-cleanup.ymlindex b8d25b96..12263ed1 100644--- a/.github/workflows/hub-cleanup.yml+++ b/.github/workflows/hub-cleanup.yml@@ -5,6 +5,11 @@# candidates from the Hub, and by 0.15.7 twelve of them sat beside the releases. This is the one# place a delete can run: the Hub credential lives only in this repository's secrets. Only tags# with "-rc." in the name are accepted; a numbered release is never deleted here.+#+# The secret must be a personal access token with the "Read, Write, Delete" scope. The release+# workflow's token needs only Read & Write, and that is what the secret held on the first run+# (2026-09-10): the login succeeded and every tag answered HTTP 403. A 403 on every tag means the+# scope, not the tag; create a Delete-scoped token in the Hub UI and set DOCKERHUB_TOKEN to it.name: hub-cleanupon:workflow_dispatch: