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

docs: the Actions 422 is account-scoped, and I said it was gone

Browse Source 
A previous commit here claimed the "Actions has been disabled for this user" 422 no
longer reproduced, citing enabled=true from
`gh api repos/hanzoai/python-sdk/actions/permissions` plus green Dependency Graph
runs. Both are true and neither is evidence: the first is repo scope, the second is
GitHub triggering its own workflow.

Dispatching still 422s as hanzo-dev. The same dispatch as zooqueen succeeds — which
is how hanzo-iam 1.30.2 finally reached PyPI at 21:05 today. The restriction is on
the account, so "are Actions enabled" and "can we trigger a workflow" are separate
questions and the repo-level check answers the wrong one.

Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in:
zooqueen
2026-07-29 14:06:04 -07:00
co-authored by Hanzo Dev
parent 35b4e61f78
commit 6009873b17
1 changed files with 9 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.hanzo/workflows/publish-pypi.yml
+9 -4
View File
@@ -12,10 +12,15 @@ name: Publish PyPI
# exchange 403s AFTER the user has already signed in through the browser.
# Depending on GitHub to ship a fix for our own CLI was the actual defect.
#
# That 422 no longer reproduces — Actions are enabled on hanzoai/python-sdk again
# and ran green on 2026-07-28. The migration stands on its own terms regardless:
# releases run on our runners, and GitHub is a mirror. Do not restore the .github
# job on the strength of the 422 having lifted.
# That 422 is still live, and it is ACCOUNT-scoped, not repo-scoped. Checking
# `gh api repos/hanzoai/python-sdk/actions/permissions` reports enabled=true, and
# GitHub's own Dependency Graph runs go green — neither tells you anything about
# dispatch. Dispatching as `hanzo-dev` returns the 422 to this day; dispatching the
# same workflow as `zooqueen` works. So "Actions are enabled" and "we can trigger a
# workflow" are different questions, and the repo-level check answers the wrong one.
#
# The migration stands on its own terms regardless: releases run on our runners and
# GitHub is a mirror. Do not restore a tag-triggered .github job.
#
# Tag -> package mapping is unchanged from the retired workflow, including the
# `hanzo-*` catch-all that maps `hanzo-v0.4.4` to the `hanzo` package.