build

fix nvrtc in cuda 12.6 #282

Sign in to view logs

Triggered via push May 14, 2025 05:47

v0.8.1

Status Success

Total duration 28m 46s

Artifacts 5

build.yaml

on: push

Matrix: build-macos

Matrix: build-windows

Publish 🐍📦 to PyPI

Matrix: build

Annotations

21 warnings

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

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

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

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

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

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

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
python-package-distributions-3.10 Expired	1.3 MB	`sha256:990b5bfb6dc8423c72a98385651c7ea799fad90bc4cc5fa56cb2a08a0642aab3`
python-package-distributions-3.11 Expired	1.3 MB	`sha256:c78acc2e1912c2f821e9205a6dfbf6dd35c6136b53d113fb289f86eaf52ad349`
python-package-distributions-3.12 Expired	1.3 MB	`sha256:e97b6813047b825f09c6e6a8d568a0636af019ff099621daed3ec6899f0d5d45`
python-package-distributions-3.13 Expired	1.3 MB	`sha256:443b5be77b257b2168c3a7f35d210611d52f8f5b3214f4f91c19cc5e1e685d46`
python-package-distributions-3.9 Expired	1.3 MB	`sha256:ea211f9798fa5ad9861ad105ef7873280d4f2c93e849b2b58a8c2bbe94e501ec`