Tag v1.53.0 (test overhaul, runtime import bug fix) #3981
tonyAnnotations
16 warnings
|
build (3.13, 2.6)
Cache not found for keys: setup-uv-1-x86_64-unknown-linux-gnu-unknown-615d16f3785028abe373358d2e33456e7dd52506a9cb14937257a13890b41f4f
|
|
build (3.13, 2.6)
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
|
|
build (3.13, 2.8)
Cache not found for keys: setup-uv-1-x86_64-unknown-linux-gnu-unknown-615d16f3785028abe373358d2e33456e7dd52506a9cb14937257a13890b41f4f
|
|
build (3.13, 3.0a)
Cache not found for keys: setup-uv-1-x86_64-unknown-linux-gnu-unknown-615d16f3785028abe373358d2e33456e7dd52506a9cb14937257a13890b41f4f
|
|
build (3.13, 3.0a)
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
|
|
build (3.13, 3.1b)
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
|
|
build (3.13, 3.1b)
Cache not found for keys: setup-uv-1-x86_64-unknown-linux-gnu-unknown-615d16f3785028abe373358d2e33456e7dd52506a9cb14937257a13890b41f4f
|
|
build (3.13, 2.7)
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
|
|
build (3.13, 2.7)
Cache not found for keys: setup-uv-1-x86_64-unknown-linux-gnu-unknown-615d16f3785028abe373358d2e33456e7dd52506a9cb14937257a13890b41f4f
|
|
build (3.13, 3.2a)
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
|
|
build (3.13, 3.2a)
Cache not found for keys: setup-uv-1-x86_64-unknown-linux-gnu-unknown-615d16f3785028abe373358d2e33456e7dd52506a9cb14937257a13890b41f4f
|
|
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):
|
|
release (3.13)
Input 'skip_existing' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `skip-existing` instead.
|
|
release (3.13)
Input 'skip_existing' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `skip-existing` instead.
|