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/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

While cibuildwheel can build CPython 3.8 universal2/arm64 wheels, we cannot test the arm64 part of them, even when running on an Apple Silicon machine. This is because we use the x86_64 installer of CPython 3.8. See the discussion in https://github.com/pypa/cibuildwheel/pull/1169 for the details. To silence this warning, set `CIBW_TEST_SKIP: "cp38-macosx_*:arm64"`.

gcc 14.2.0 is already installed and up-to-date. To reinstall 14.2.0, run: brew reinstall gcc

gcc 14.2.0 is already installed and up-to-date. To reinstall 14.2.0, run: brew reinstall gcc

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.

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

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):

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.

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

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):

Setting DIST_EXTRA_CONFIG=C:\Users\runneradmin\AppData\Local\Temp\cibw-run-3c7a3v5d\cp39-win_arm64\build\extra-setup.cfg for cross-compilation

Setting SETUPTOOLS_EXT_SUFFIX=.cp39-win_arm64.pyd for cross-compilation

Setting SETUPTOOLS_USE_DISTUTILS=local as it is required for cross-compilation

Setting CARGO_BUILD_TARGET=aarch64-pc-windows-msvc for cross-compilation

Setting DIST_EXTRA_CONFIG=C:\Users\runneradmin\AppData\Local\Temp\cibw-run-3c7a3v5d\cp310-win_arm64\build\extra-setup.cfg for cross-compilation

Setting SETUPTOOLS_EXT_SUFFIX=.cp310-win_arm64.pyd for cross-compilation

Setting SETUPTOOLS_USE_DISTUTILS=local as it is required for cross-compilation

Setting CARGO_BUILD_TARGET=aarch64-pc-windows-msvc for cross-compilation

Setting DIST_EXTRA_CONFIG=C:\Users\runneradmin\AppData\Local\Temp\cibw-run-3c7a3v5d\cp311-win_arm64\build\extra-setup.cfg for cross-compilation

Setting SETUPTOOLS_EXT_SUFFIX=.cp311-win_arm64.pyd for cross-compilation