Skip to content

v14.0.1

v14.0.1 #1313

Triggered via release December 6, 2024 08:45
@WyattBlueWyattBlue
published v14.0.1
Status Success
Total duration 3h 9m 16s
Artifacts 7

tests.yml

on: release
Matrix: package-wheel
package-source
22s
package-source
Fit to window
Zoom out
Zoom in

Annotations

20 warnings
package-source
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
package-wheel (macos-14, arm64)
PyPy builds will be disabled by default in version 3. Enabling PyPy builds should be specified by enable
package-wheel (macos-14, arm64)
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
package-wheel (windows-latest, AMD64)
PyPy builds will be disabled by default in version 3. Enabling PyPy builds should be specified by enable
package-wheel (windows-latest, AMD64)
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
package-wheel (ubuntu-latest, x86_64)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
package-wheel (ubuntu-latest, x86_64)
PyPy builds will be disabled by default in version 3. Enabling PyPy builds should be specified by enable
package-wheel (ubuntu-latest, x86_64)
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
package-wheel (ubuntu-latest, i686)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
package-wheel (ubuntu-latest, i686)
PyPy builds will be disabled by default in version 3. Enabling PyPy builds should be specified by enable
package-wheel (ubuntu-latest, i686)
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
package-wheel (macos-13, x86_64)
pkgconf 2.3.0_1 is already installed and up-to-date. To reinstall 2.3.0_1, run: brew reinstall pkgconf
package-wheel (macos-13, x86_64)
PyPy builds will be disabled by default in version 3. Enabling PyPy builds should be specified by enable
package-wheel (macos-13, x86_64)
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
package-wheel (ubuntu-latest, aarch64)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
package-wheel (ubuntu-latest, aarch64)
PyPy builds will be disabled by default in version 3. Enabling PyPy builds should be specified by enable
package-wheel (ubuntu-latest, aarch64)
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
dist-macos-13-x86_64
161 MB
dist-macos-14-arm64
129 MB
dist-source
3.74 MB
dist-ubuntu-latest-aarch64
194 MB
dist-ubuntu-latest-i686
191 MB
dist-ubuntu-latest-x86_64
206 MB
dist-windows-latest-AMD64
171 MB