Skip to content

chore(deps): lock file maintenance #13853

chore(deps): lock file maintenance

chore(deps): lock file maintenance #13853

Triggered via pull request March 4, 2024 00:13
Status Success
Total duration 5m 20s
Artifacts 1

test.yml

on: pull_request
Test with multiple repositories
13s
Test with multiple repositories
Test changed-files using since and until
0s
Test changed-files using since and until
Test changed-files similar base and commit sha
5s
Test changed-files similar base and commit sha
Test using branch names for base_sha and sha inputs
9s
Test using branch names for base_sha and sha inputs
Test changed-files with pull request head ref
5s
Test changed-files with pull request head ref
Test changed-files non existent base sha
12s
Test changed-files non existent base sha
Test changed-files non existent sha
12s
Test changed-files non existent sha
Test changed-files with REST API
6s
Test changed-files with REST API
Test changed-files with non existing repository
0s
Test changed-files with non existing repository
Test dir names deleted files include only deleted dirs single file
9s
Test dir names deleted files include only deleted dirs single file
Test dir names deleted files include only deleted dirs
7s
Test dir names deleted files include only deleted dirs
Matrix: Test changed-files with limited commit history
Matrix: Test changed-files with pull request without persist credentials
Matrix: Test changed-files recover deleted file
Matrix: Test changed-files since last remote commit
Matrix: Test changed-files with submodule
Matrix: Test changed-files with yaml
Matrix: Test changed-files
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 5 warnings
build
Process completed with exit code 1.
Test changed-files similar base and commit sha
Similar commit hashes detected: previous sha: d1c0ee4e67338c2c3e50a08b6156ab8c155be21c is equivalent to the current sha: d1c0ee4e67338c2c3e50a08b6156ab8c155be21c.
Test changed-files similar base and commit sha
Please verify that both commits are valid, and increase the fetch_depth to a number higher than 50.
Test changed-files similar base and commit sha
Similar commit hashes detected.
Test changed-files since last remote commit (1)
Unable to locate the previous commit in the local history. Please ensure to checkout pull request HEAD commit instead of the merge commit. See: https://github.com/actions/checkout/blob/main/README.md#checkout-pull-request-head-commit-instead-of-merge-commit
build
Input "sha" is not supported when using GitHub's REST API to get changed files
Test changed-files with limited commit history (1, 1)
Unable to find merge base between 0a392e7438f4e555202d05c463827135b3a3e289 and b7eff15122e78907e398ae5c09fc0d7dd3b957c2
Test changed-files with limited commit history (1, 2)
Unable to find merge base between 0a392e7438f4e555202d05c463827135b3a3e289 and b7eff15122e78907e398ae5c09fc0d7dd3b957c2
Test changed-files since last remote commit (2)
Unable to locate the commit sha: 534774ed4f094f859820d1903cf8a22f5a8e1c3e
Test changed-files since last remote commit (1)
Unable to locate the commit sha: 534774ed4f094f859820d1903cf8a22f5a8e1c3e

Artifacts

Produced during runtime
Name Size
build-assets Expired
926 KB