Skip to content

Merge pull request #830 from roboflow/feature/update_fps_monitor_api #24

Merge pull request #830 from roboflow/feature/update_fps_monitor_api

Merge pull request #830 from roboflow/feature/update_fps_monitor_api #24

Triggered via push January 31, 2024 21:36
Status Failure
Total duration 53s
Artifacts

publish-test.yml

on: push
Build and publish to PyPI
45s
Build and publish to PyPI
Fit to window
Zoom out
Zoom in

Annotations

1 error, 2 warnings, and 2 notices
Password-based uploads deprecated
Starting in 2024, PyPI will require all users to enable Two-Factor Authentication. This will consequently require all users to switch to either Trusted Publishers (preferred) or API tokens for package uploads. Read more: https://blog.pypi.org/posts/2023-05-25-securing-pypi-with-2fa/
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
Build and publish to PyPI
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
Build and publish to PyPI
Using a username + password pair for authentication against https://test.pypi.org/legacy/