hanzoai/python-sdk
2
0
Fork 0
mirror of https://github.com/hanzoai/python-sdk.git synced 2026-10-23 20:23:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

hanzo.yml: name the cloud this SDK is a projection of

Browse Source 
hanzoai/ci defaults client.spec.repo to hanzoai/cloud, and that repo is now the
re-rooted OSS core -- a short line sharing no ancestor with the product. The
ref this projection is pinned to does not exist there, so every run of the
client lane, check or move, died fetching it: `curl: (22) ... 404`.

Measured: the same token reads openapi.yaml at 113cf7d6 from hanzo-inc/cloud
with a 200 and from hanzoai/cloud with a 404. Nothing about the credential.

`.spec-lock`'s own repo= line does not set this -- ci reads the repo from
hanzo.yml and uses the lock's copy for a commit message -- so the two could
disagree in silence, and did. They are one fact and now agree.

Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in:
zeekay
2026-08-19 22:57:53 -07:00
co-authored by Hanzo Dev
parent 208240ecff
commit 7b80afeb4a
1 changed files with 15 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
hanzo.yml
+15
View File
@@ -202,5 +202,20 @@ test:
# and is 1814 now, which is the point: it grows from the routers rather than from
# an editor, so a true document overtook the unverified one on its own.
client:
# WHICH cloud, said out loud. hanzoai/ci defaults this to `hanzoai/cloud`, and
# that repo is now the re-rooted OSS core — a short line sharing no ancestor
# with the product. So the default resolved to a tree that does not contain the
# ref this projection is pinned to, and every run of the client lane, check or
# move, died on `curl: (22) ... 404` fetching a document that was never there.
#
# It reads as a credential problem and is not one: the same token fetches the
# same ref from hanzo-inc/cloud with a 200. The product line is the one whose
# openapi.yaml this SDK is a projection of, so it is the one named here.
#
# This is also the field `.spec-lock`'s own `repo=` line does NOT set — ci reads
# the repo from here and uses the lock's copy only for a commit message, so the
# two can disagree silently. They are one fact; keep them equal.
spec:
repo: hanzo-inc/cloud
generate: ./scripts/generate.sh
version: "pyproject.toml:grep -m1 '^version' pyproject.toml | sed -E 's/.*\"(.*)\".*/\\1/'"