v0.2.16 #42
salccAnnotations
6 warnings
|
test (3.8)
Cache not found for keys: setup-python-Linux-x64-24.04-Ubuntu-python-3.8.18-pip-c8380ca3c4aafd27e18cea895761cfccda51319399b3102a729d9f7d39f06a9c, setup-python-Linux-x64-24.04-Ubuntu-python-3.8.18-pip
|
|
test (3.13)
Cache not found for keys: setup-python-Linux-x64-24.04-Ubuntu-python-3.13.2-pip-c8380ca3c4aafd27e18cea895761cfccda51319399b3102a729d9f7d39f06a9c, setup-python-Linux-x64-24.04-Ubuntu-python-3.13.2-pip
|
|
test (3.13)
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
|
|
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 | |
|---|---|---|
|
github-pages
Expired
|
945 KB |
|