Skip to content

"403 Invalid API Token: caveat must be an array" when using hatch publish #15586

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mcarans opened this issue Mar 13, 2024 · 4 comments
Closed
Labels
bug 🐛 requires triaging maintainers need to do initial inspection of issue

Comments

@mcarans
Copy link

mcarans commented Mar 13, 2024

Describe the bug
I receive the following error when using hatch publish for a package that has been published fine many times before:

Error uploading to repository: https://upload.pypi.org/legacy/ - Client error '403 Invalid API Token: caveat must be an array' for url 'https://upload.pypi.org/legacy/'

I have not changed anything to do with the publishing (HATCH_INDEX_USER and HATCH_INDEX_AUTH are the same and I haven't touched pyproject.toml).

Expected behavior
Package is published

To Reproduce
Publish a package using hatch in a GitHub Actions workflow

My Platform
I'm running the publish workflow in GitHub Actions. You can see it here if it's any help:
https://github.com/OCHA-DAP/hdx-python-utilities/blob/main/.github/workflows/publish.yaml

@mcarans mcarans added bug 🐛 requires triaging maintainers need to do initial inspection of issue labels Mar 13, 2024
@Kelsey-Ethyca
Copy link

I am getting this same error using twine

@HubTou

This comment was marked as duplicate.

@di
Copy link
Member

di commented Mar 13, 2024

Thanks, I'm looking into this. Please avoid adding "+1" or "me too" comments and 👍 the top-level comment if you're affected instead.

@di
Copy link
Member

di commented Mar 13, 2024

This should now be resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 requires triaging maintainers need to do initial inspection of issue
Projects
None yet
Development

No branches or pull requests

4 participants