follow the release pointer the rest of the fleet follows

This repo pinned an exact hanzoai/ci release, so it kept running the build.yml
that reads git.hanzo.ai through HANZO_GIT_TOKEN — a credential no org seals.
The gate has been red on that ever since, while the sixty-four repos on @v1
moved past it.

@v1 is not an unproven tip. hanzoai/ci pins its own gate to the last release and
moves that pin first, so a release proves itself there before @v1 follows it.
An exact pin here opts out of that and rots instead.

Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in:
2026-08-20 19:53:49 -07:00
co-authored by Hanzo Dev
parent 93af3004c6
commit d301b245e2
+1 -1
View File
@@ -62,7 +62,7 @@ on:
default: ''
jobs:
cicd:
uses: hanzoai/ci/.hanzo/workflows/build.yml@v1.0.77
uses: hanzoai/ci/.hanzo/workflows/build.yml@v1
with:
spec-ref: ${{ github.event.inputs.spec-ref || '' }}
spec-version: ${{ github.event.inputs.spec-version || '' }}