From b01ad0c608c0bae9bdb1fd2d31f56c695b592de9 Mon Sep 17 00:00:00 2001 From: Abhishek Krishna Date: Mon, 1 Jun 2026 14:07:45 +0530 Subject: [PATCH] fix(release): correct PYPI_TOKEN error message in check-release-environment The script checks for the PYPI_TOKEN env var, but the error message only mentioned HANZO_PYPI_TOKEN. CI workflows actually map either the HANZO_PYPI_TOKEN or PYPI_TOKEN secret into PYPI_TOKEN (see .github/workflows/publish-pypi.yml and release-doctor.yml), so the message was misleading when the variable was missing. Update the text to match the real behaviour. --- bin/check-release-environment | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bin/check-release-environment b/bin/check-release-environment index d6f7bbb1..c46ddb9c 100644 --- a/bin/check-release-environment +++ b/bin/check-release-environment @@ -3,7 +3,7 @@ errors=() if [ -z "${PYPI_TOKEN}" ]; then - errors+=("The HANZO_PYPI_TOKEN secret has not been set. Please set it in either this repository's secrets or your organization secrets.") + errors+=("The PYPI_TOKEN environment variable has not been set (CI maps it from either the HANZO_PYPI_TOKEN or PYPI_TOKEN secret). Please set one of those secrets in this repository or your organization secrets.") fi lenErrors=${#errors[@]}