Create Release #14
JarryShawcreate-release.yml
on: push
Annotations
6 errors, 9 warnings, and 8 notices
|
PyPI distribution for Python 3.8
Not Found
|
|
PyPI distribution for Python 3.9
The job was canceled because "_3_8" failed.
|
|
PyPI distribution for Python pypy3.9
The job was canceled because "_3_8" failed.
|
|
PyPI distribution for Python pypy3.9
The operation was canceled.
|
|
PyPI distribution for Python pypy3.8
The job was canceled because "_3_8" failed.
|
|
PyPI distribution for Python pypy3.8
The operation was canceled.
|
|
PyPI distribution for Python 3.11
Using a user-provided API token for authentication against https://test.pypi.org/legacy/
|
|
PyPI distribution for Python 3.11
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
|
PyPI distribution for Python 3.10
Using a user-provided API token for authentication against https://test.pypi.org/legacy/
|
|
PyPI distribution for Python 3.10
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
|
PyPI distribution for Python 3.8
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
|
PyPI distribution for Python 3.8
Using a user-provided API token for authentication against https://test.pypi.org/legacy/
|
|
PyPI distribution for Python 3.9
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
|
PyPI distribution for Python 3.9
Using a user-provided API token for authentication against https://test.pypi.org/legacy/
|
|
GitHub Release
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|