chore: Bump release 0.5.dev0 #1068
ci_cd.yml
on: push
Documentation Style Check
17s
Code style
1m 0s
Check the name of the PR
0s
Matrix: Build and Smoke tests
Matrix: Tests
Release project to private, public PyPI and GitHub
57s
Deploy development documentation
0s
Deploy stable docs
0s
Annotations
8 warnings and 2 notices
Build and Smoke tests (ubuntu-latest, 3.11)
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 and Smoke tests (ubuntu-latest, 3.12)
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 and Smoke tests (ubuntu-latest, 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
|
Build and Smoke tests (windows-latest, 3.10)
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 and Smoke tests (windows-latest, 3.11)
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 and Smoke tests (windows-latest, 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
|
Build and Smoke tests (windows-latest, 3.12)
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 documentation
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
|
Release project to private, public PyPI and GitHub
We recommend using trusted publishers to securely publish packages on PyPI. You should consider moving to this approach.
|
Release project to private, public PyPI and GitHub
We recommend using trusted publishers to securely publish packages on PyPI. You should consider moving to this approach.
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
ansys-units-artifacts
|
49.8 KB |
|
ansys-units-v0.5.dev0-wheelhouse-ubuntu-latest-3.10
|
792 KB |
|
ansys-units-v0.5.dev0-wheelhouse-ubuntu-latest-3.11
|
804 KB |
|
ansys-units-v0.5.dev0-wheelhouse-ubuntu-latest-3.12
|
808 KB |
|
ansys-units-v0.5.dev0-wheelhouse-ubuntu-latest-3.13
|
800 KB |
|
ansys-units-v0.5.dev0-wheelhouse-windows-latest-3.10
|
219 KB |
|
ansys-units-v0.5.dev0-wheelhouse-windows-latest-3.11
|
219 KB |
|
ansys-units-v0.5.dev0-wheelhouse-windows-latest-3.12
|
213 KB |
|
ansys-units-v0.5.dev0-wheelhouse-windows-latest-3.13
|
214 KB |
|
documentation-html
|
7.84 MB |
|
documentation-pdf
|
331 KB |
|