pypi_build_and_images.yaml
on: push
Matrix: Build_and_upload_to_pypi
Matrix: Build_images
Annotations
13 warnings and 13 notices
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
|
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
|
Build_and_upload_to_pypi (reqmgr2ms-output) / build_and_publish_from_template
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Build_and_upload_to_pypi (reqmgr2ms-transferor) / build_and_publish_from_template
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Build_and_upload_to_pypi (global-workqueue) / build_and_publish_from_template
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Build_and_upload_to_pypi (reqmgr2ms-unmerged) / build_and_publish_from_template
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Build_and_upload_to_pypi (reqmgr2ms-monitor) / build_and_publish_from_template
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Build_and_upload_to_pypi (reqmgr2ms-rulecleaner) / build_and_publish_from_template
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Build_and_upload_to_pypi (reqmon) / build_and_publish_from_template
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Build_and_upload_to_pypi (wmagent) / build_and_publish_from_template
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Build_and_upload_to_pypi (acdcserver) / build_and_publish_from_template
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Build_and_upload_to_pypi (wmagent-devtools) / build_and_publish_from_template
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Build_and_upload_to_pypi (wmcore) / build_and_publish_from_template
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Build_and_upload_to_pypi (reqmgr2ms-pileup) / build_and_publish_from_template
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
Build_and_upload_to_pypi (reqmgr2) / build_and_publish_from_template
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|