Skip to content

pyKVFinder v0.8.0

pyKVFinder v0.8.0 #49

Triggered via release April 27, 2025 08:10
@jvsguerrajvsguerra
published v0.8.0
Status Success
Total duration 42m 1s
Artifacts 5

deploy.yml

on: release
Matrix: build_wheels
Build source distribution
1m 46s
Build source distribution
Upload release to PyPI
45s
Upload release to PyPI
Fit to window
Zoom out
Zoom in

Annotations

15 warnings
Build wheels on macos-latest
llvm 20.1.3 is already installed and up-to-date. To reinstall 20.1.3, run: brew reinstall llvm
Build wheels on macos-latest
libomp 20.1.3 is already installed and up-to-date. To reinstall 20.1.3, run: brew reinstall libomp
Build wheels on macos-latest
llvm 20.1.3 is already installed and up-to-date. To reinstall 20.1.3, run: brew reinstall llvm
Build wheels on macos-latest
libomp 20.1.3 is already installed and up-to-date. To reinstall 20.1.3, run: brew reinstall libomp
Build wheels on macos-latest
llvm 20.1.3 is already installed and up-to-date. To reinstall 20.1.3, run: brew reinstall llvm
Build wheels on macos-latest
libomp 20.1.3 is already installed and up-to-date. To reinstall 20.1.3, run: brew reinstall libomp
Build wheels on macos-15
llvm 20.1.3 is already installed and up-to-date. To reinstall 20.1.3, run: brew reinstall llvm
Build wheels on macos-15
libomp 20.1.3 is already installed and up-to-date. To reinstall 20.1.3, run: brew reinstall libomp
Build wheels on macos-15
llvm 20.1.3 is already installed and up-to-date. To reinstall 20.1.3, run: brew reinstall llvm
Build wheels on macos-15
libomp 20.1.3 is already installed and up-to-date. To reinstall 20.1.3, run: brew reinstall libomp
Build wheels on macos-15
llvm 20.1.3 is already installed and up-to-date. To reinstall 20.1.3, run: brew reinstall llvm
Build wheels on macos-15
libomp 20.1.3 is already installed and up-to-date. To reinstall 20.1.3, run: brew reinstall libomp
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
artifacts-macos-15 Expired
1.84 MB
sha256:9ecead8d134738def68cca3e345d07ae85da031297cc063d11f6302cb0966619
artifacts-macos-latest Expired
1.84 MB
sha256:95c8826115e67a7ca36355c13756d5627b114fac115670175fa0dcb687b97c07
artifacts-sdist Expired
205 KB
sha256:826257c15ea1b7c690c794ba19dcfdfbb8e452e6d23ecea2416242da0af3f7c4
artifacts-ubuntu-latest Expired
4.73 MB
sha256:623e0b146c27c31a95ce3a5ac5c28bbbfa0880ea2c95c0bec4b7f91d928f5528
artifacts-windows-latest Expired
962 KB
sha256:fd7e7b6c2a101e26982d327657dc9384ea5a9c33fb37b0070b39567e52cee7f1