Skip to content

Full cache for offline mode #449

Full cache for offline mode

Full cache for offline mode #449

Triggered via pull request April 21, 2026 06:44
Status Success
Total duration 4m 15s
Artifacts 4

pre-merge.yml

on: pull_request
pre-merge  /  sanitize-project-folder
2s
pre-merge / sanitize-project-folder
pre-merge  /  license-compliance-check
0s
pre-merge / license-compliance-check
pre-merge  /  run-repo-pipelines
3m 56s
pre-merge / run-repo-pipelines
pre-merge  /  zizmor-scan
11s
pre-merge / zizmor-scan
pre-merge  /  secrets-gitleaks-scan
15s
pre-merge / secrets-gitleaks-scan
pre-merge  /  trivy-filesystem-scan
20s
pre-merge / trivy-filesystem-scan
pre-merge  /  trivy-critical-scan
16s
pre-merge / trivy-critical-scan
pre-merge  /  trivy-config-scan
12s
pre-merge / trivy-config-scan
pre-merge  /  bandit
17s
pre-merge / bandit
Matrix: pre-merge / Scan Docker Images for CIS
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
pre-merge / zizmor-scan
No file matched to [/home/runner/work/image-composer-tool/image-composer-tool/**/*requirements*.txt,/home/runner/work/image-composer-tool/image-composer-tool/**/*requirements*.in,/home/runner/work/image-composer-tool/image-composer-tool/**/*constraints*.txt,/home/runner/work/image-composer-tool/image-composer-tool/**/*constraints*.in,/home/runner/work/image-composer-tool/image-composer-tool/**/pyproject.toml,/home/runner/work/image-composer-tool/image-composer-tool/**/uv.lock,/home/runner/work/image-composer-tool/image-composer-tool/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
pre-merge / trivy-config-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
pre-merge / secrets-gitleaks-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
pre-merge / trivy-critical-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
pre-merge / trivy-filesystem-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
gitleaks-results-vq9n90-image-composer-tool
175 Bytes
sha256:80fbcd812e5a217fcff9edcf327b5e768ff2fb064d2a974468f5fde6ed2c358e
trivy-config-scan-image-composer-tool
496 Bytes
sha256:6c48433d2e4eae6c4d302b6180a495d7286326122bf97d9675c452aeb2766a21
trivy-fs-scan-report-image-composer-tool
1.29 KB
sha256:d707403550870b161883f00f64598362a71449f61b06f6d7fde84daed159f7ac
zizmor-scan-report-image-composer-tool
594 Bytes
sha256:4712b1b81ccbfe51d38e9690f2112decf0db0331057ec72467e1fb38e4d8580c