Skip to content

23.9.17rc0

23.9.17rc0 #61

Triggered via release September 17, 2023 19:33
Status Success
Total duration 1m 13s
Artifacts 1

build.yaml

on: release
🔨 Build distribution
22s
🔨 Build distribution
zip-asset-upload
5s
zip-asset-upload
📦 Publish tagged releases to PyPI
33s
📦 Publish tagged releases to PyPI
📧 Notify Pioreactor/CustoPizer
5s
📧 Notify Pioreactor/CustoPizer
Fit to window
Zoom out
Zoom in

Annotations

4 warnings and 1 notice
🔨 Build distribution
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
zip-asset-upload
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
📧 Notify Pioreactor/CustoPizer
The following actions uses node12 which is deprecated and will be forced to run on node16: peter-evans/repository-dispatch@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
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
📦 Publish tagged releases to PyPI
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/

Artifacts

Produced during runtime
Name Size
dist Expired
186 KB