Skip to content

version bump

version bump #277

Triggered via push December 12, 2023 18:12
Status Success
Total duration 13m 38s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention
Matrix: test-n-publish
Fit to window
Zoom out
Zoom in

Annotations

8 warnings and 4 notices
test-n-publish (3.8)
Input 'skip_existing' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `skip-existing` 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
test-n-publish (3.9)
Input 'skip_existing' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `skip-existing` 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
test-n-publish (3.10)
Input 'skip_existing' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `skip-existing` 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
test-n-publish (3.11)
Input 'skip_existing' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `skip-existing` 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
test-n-publish (3.8)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
test-n-publish (3.9)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
test-n-publish (3.10)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
test-n-publish (3.11)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/