ci(release): Preparing v0.0.2 #566
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
ci.yaml
on: pull_request
Validate PR Title
2s
pre-commit
2m 22s
Validate Lockfile
1m 54s
Validating commits
15s
Linting
10m 55s
Test & Coverage
12m 14s
Annotations
18 warnings and 4 notices
Validating commits
Failed to restore: Cache service responded with 429
|
Validate Lockfile
Failed to restore: Cache service responded with 429
|
Validate Lockfile
Failed to restore: Cache service responded with 429
|
Validate Lockfile
Failed to restore: Cache service responded with 429
|
Validate Lockfile
Failed to save: Cache service responded with 429 during commit cache.
|
pre-commit
Failed to restore: Cache service responded with 429
|
pre-commit
Failed to restore: Cache service responded with 429
|
pre-commit
Failed to restore: Cache service responded with 429
|
pre-commit
Failed to restore: Cache service responded with 429
|
pre-commit
Failed to save: Cache service responded with 429 during commit cache.
|
pre-commit
Failed to save: Cache service responded with 429 during commit cache.
|
pre-commit
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Linting
Failed to restore: Cache service responded with 429
|
Linting
Failed to restore: Cache service responded with 429
|
Linting
Failed to restore: Cache service responded with 429
|
Test & Coverage
Failed to restore: Cache service responded with 429
|
Test & Coverage
Failed to restore: Cache service responded with 429
|
Test & Coverage
Failed to restore: Cache service responded with 429
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
sccache stats
16% - 227 hits, 1220 misses, 0 errors
|
sccache stats
14% - 167 hits, 1051 misses, 0 errors
|