fix CI release #56
ci.yml
on: push
Annotations
14 warnings
3.9
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
3.12
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
3.11
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
3.8
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
3.13
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Build source distribution
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
macos-latest
cibuildwheel 3 will require Python 3.11+, please upgrade the Python version used to run cibuildwheel. This does not affect the versions you can target when building wheels. See: https://cibuildwheel.pypa.io/en/stable/#what-does-it-do
|
ubuntu-latest
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
ubuntu-latest
cibuildwheel 3 will require Python 3.11+, please upgrade the Python version used to run cibuildwheel. This does not affect the versions you can target when building wheels. See: https://cibuildwheel.pypa.io/en/stable/#what-does-it-do
|
windows-latest
cibuildwheel 3 will require Python 3.11+, please upgrade the Python version used to run cibuildwheel. This does not affect the versions you can target when building wheels. See: https://cibuildwheel.pypa.io/en/stable/#what-does-it-do
|
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
|
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
|
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):
|
Artifacts
Produced during runtime
Name | Size | Digest | |
---|---|---|---|
vtzero-sdist
Expired
|
128 KB |
sha256:08b52d18d0c7bd6b15eff2af5f99799e8763c8f445a4755b1d4badda0b496494
|
|
vtzero-wheels-macos-latest-2
Expired
|
1.92 MB |
sha256:fc3d649f8c2d1196808f560ee5032aa09d54372d87cf45855c1db27853cd2c40
|
|
vtzero-wheels-ubuntu-latest-0
Expired
|
24.4 MB |
sha256:ba3eb1b0cb852de62a812f9663ceebee6f6ea6924b755f073fc0871853969ef5
|
|
vtzero-wheels-windows-latest-1
Expired
|
1.53 MB |
sha256:6fa5eaebe09a9820a312052e0f2e7c34e9044e311cec8cdfb4432da4e5c4fbd9
|
|