Cache not found for keys: node-cache-macOS-arm64-npm-efa6928da2013e679096d333c9a1d906f40115ce7526b329a15f49d9e27e37bf

Cache not found for keys: node-cache-Windows-x64-npm-efa6928da2013e679096d333c9a1d906f40115ce7526b329a15f49d9e27e37bf

Cache not found for keys: node-cache-Linux-x64-npm-efa6928da2013e679096d333c9a1d906f40115ce7526b329a15f49d9e27e37bf

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

Cache not found for keys: node-cache-Linux-x64-npm-efa6928da2013e679096d333c9a1d906f40115ce7526b329a15f49d9e27e37bf

Cache not found for keys: docker.io--tonistiigi--binfmt-latest-linux-x64

Cache not found for keys: v0-rust-package-Linux-26ad3c07-2855c779, v0-rust-package-Linux-26ad3c07

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-xsphxc1i\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