Repository navigation
Update all dependencies #29
Triggered via pull request
October 3, 2026 07:10
renovate[bot]
renovate[bot]
synchronize
#115
Status
Failure
Total duration
54s
Artifacts
–
github_actions_scan.yml Required
on: pull_request_target
Annotations
10 errors, 4 warnings, and 5 notices
|
zizmor-output
Process completed with exit code 1.
|
|
zizmor/unpinned-uses:
.github/workflows/build.yml#L33
unpinned action reference: action is not pinned to a hash (required by blanket policy)
|
|
zizmor/unpinned-uses:
.github/workflows/build.yml#L27
unpinned action reference: action is not pinned to a hash (required by blanket policy)
|
|
zizmor/unpinned-uses:
.github/workflows/build.yml#L24
unpinned action reference: action is not pinned to a hash (required by blanket policy)
|
|
zizmor/unpinned-uses:
.github/workflows/build.yml#L21
unpinned action reference: action is not pinned to a hash (required by blanket policy)
|
|
zizmor-output
Found 4 findings for mandatory checks that must always succeed.
|
|
unpinned-uses:
.github/workflows/build.yml#L33
build.yml:33: unpinned action reference: action is not pinned to a hash (required by blanket policy)
|
|
unpinned-uses:
.github/workflows/build.yml#L27
build.yml:27: unpinned action reference: action is not pinned to a hash (required by blanket policy)
|
|
unpinned-uses:
.github/workflows/build.yml#L24
build.yml:24: unpinned action reference: action is not pinned to a hash (required by blanket policy)
|
|
unpinned-uses:
.github/workflows/build.yml#L21
build.yml:21: unpinned action reference: action is not pinned to a hash (required by blanket policy)
|
|
Workflow execution policy warning (evaluate mode):
google-gh-automation/workflows/.github/workflows/github_actions_scan.yml#L1
On November 2, 2026, GitHub will restrict `pull_request_target` on public repositories by default. To continue allowing the event trigger, configure an Actions policy. Learn more: https://gh.io/securely-using-pull_request_target#default-policy-for-pull_request_target
|
|
zizmor-config
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: google-github-actions/auth@c200f3691d83b41bf9bbd8638997a462592937ed. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
archived-uses:
.github/workflows/build.yml#L33
build.yml:33: action or reusable workflow from archived repository: repository is archived
|
|
zizmor-upload
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: google-github-actions/auth@c200f3691d83b41bf9bbd8638997a462592937ed. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
check-changes
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
|
|
zizmor-config
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
|
|
zizmor-scan
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
|
|
zizmor-output
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
|
|
zizmor-upload
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
|