Skip to content

Create cleanup_workspace #453

Create cleanup_workspace

Create cleanup_workspace #453

Triggered via pull request April 21, 2026 21:49
Status Success
Total duration 3m 52s
Artifacts 4

pre-merge.yml

on: pull_request
pre-merge  /  sanitize-project-folder
2s
pre-merge / sanitize-project-folder
pre-merge  /  license-compliance-check
pre-merge / license-compliance-check
pre-merge  /  run-repo-pipelines
3m 35s
pre-merge / run-repo-pipelines
pre-merge  /  zizmor-scan
8s
pre-merge / zizmor-scan
pre-merge  /  secrets-gitleaks-scan
14s
pre-merge / secrets-gitleaks-scan
pre-merge  /  trivy-filesystem-scan
15s
pre-merge / trivy-filesystem-scan
pre-merge  /  trivy-critical-scan
14s
pre-merge / trivy-critical-scan
pre-merge  /  trivy-config-scan
10s
pre-merge / trivy-config-scan
pre-merge  /  bandit
13s
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-momeb8-image-composer-tool
175 Bytes
sha256:eae3e5b4a5e82811fe3fb20f2df5b88969279bc766321c0e8aad7577d57359d1
trivy-config-scan-image-composer-tool
496 Bytes
sha256:055177ac34b22b8a150d816f10d9fa4adaab4566cdf6b0e06658a7b3ca116c34
trivy-fs-scan-report-image-composer-tool
1.29 KB
sha256:628dcc90c2d2581fc54e2f20a7ed322efded589d7919183e54a9d2d852e1f574
zizmor-scan-report-image-composer-tool
594 Bytes
sha256:efc4fe78af659fc4b31b676264be0443c1b3b752a547433afc65534c3626f366