Update templated files to rev d426b5d #1465
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
build.yml
on: pull_request
Matrix: Run Cargo Deny
Select target helm repository based on action trigger
0s
Run Cargo Udeps
1m 21s
Run Rustfmt
14s
Run Clippy
27s
Run RustDoc
58s
Run Cargo Tests
31s
Check if committed README is the one we would render from the available parts
20s
Check if committed Helm charts are up to date
45s
Matrix: package_and_publish
Build and publish manifest list
52s
Run the OpenShift Preflight check on the published images
2s
Annotations
3 errors and 1 warning
[actionlint] .github/workflows/build.yml#L307:
.github/workflows/build.yml#L307
label "buildjet-2vcpu-ubuntu-2204-arm" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2022", "windows-2019", "windows-2016", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-22.04", "ubuntu-20.04", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-14.0", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "macos-13.0", "macos-12-xl", "macos-12-xlarge", "macos-12-large", "macos-12", "macos-12.0", "macos-11", "macos-11.0", "macos-10.15", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file [runner-label]
|
[actionlint] .github/workflows/build.yml#L429:
.github/workflows/build.yml#L429
shellcheck reported issue in this script: SC2002:style:1:10: Useless cat. Consider 'cmd < file | ..' or 'cmd file | ..' instead [shellcheck]
|
Run the OpenShift Preflight check on the published images
Process completed with exit code 1.
|
Run Clippy
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: giraffate/clippy-action@13b9d32482f25d29ead141b79e7e04e7900281e0. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|