Publish to TestPyPI #5
NekoAria
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
Annotations
2 errors, 6 warnings, and 3 notices
|
deploy (3.8)
The job was canceled because "_3_9" failed.
|
|
deploy (3.8)
The operation was canceled.
|
|
deploy (3.11)
Input 'repository_url' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `repository-url` instead.
|
|
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
|
|
deploy (3.9)
Input 'repository_url' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `repository-url` instead.
|
|
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
|
|
deploy (3.10)
Input 'repository_url' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `repository-url` instead.
|
|
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
|
|
deploy (3.11)
Using a user-provided API token for authentication against https://test.pypi.org/legacy/
|
|
deploy (3.9)
Using a user-provided API token for authentication against https://test.pypi.org/legacy/
|
|
deploy (3.10)
Using a user-provided API token for authentication against https://test.pypi.org/legacy/
|