Fix github workflows #4
codophobiaAnnotations
2 errors, 4 warnings, and 2 notices
|
build (3.10)
The job was canceled because "_3_9" failed.
|
|
build (3.10)
The operation was canceled.
|
|
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
|
|
build (3.8):
# >> PyPA publish to PyPI GHA: POTENTIALLY INVALID TOKEN <<#L1
It looks like you are trying to use an API token to authenticate in the package index and your token value does not start with "pypi-" as it typically should. This may cause an authentication error. Please verify that you have copied your token properly if such an error occurs.
|
|
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
|
|
build (3.9):
# >> PyPA publish to PyPI GHA: POTENTIALLY INVALID TOKEN <<#L1
It looks like you are trying to use an API token to authenticate in the package index and your token value does not start with "pypi-" as it typically should. This may cause an authentication error. Please verify that you have copied your token properly if such an error occurs.
|
|
build (3.8)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
|
build (3.9)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|