Skip to content

Added support for customizable GPT partition index #439

Added support for customizable GPT partition index

Added support for customizable GPT partition index #439

Re-run triggered April 21, 2026 05:42
Status Success
Total duration 2m 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
pre-merge / license-compliance-check
pre-merge  /  run-repo-pipelines
1m 53s
pre-merge / run-repo-pipelines
pre-merge  /  zizmor-scan
9s
pre-merge / zizmor-scan
pre-merge  /  secrets-gitleaks-scan
19s
pre-merge / secrets-gitleaks-scan
pre-merge  /  trivy-filesystem-scan
15s
pre-merge / trivy-filesystem-scan
pre-merge  /  trivy-critical-scan
22s
pre-merge / trivy-critical-scan
pre-merge  /  trivy-config-scan
18s
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-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/
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-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 / 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/

Artifacts

Produced during runtime
Name Size Digest
gitleaks-results-6bc53a-image-composer-tool
175 Bytes
sha256:7d720a226779be956db8abc0baa44025e612aaf5feafe48f6bb9d9d537c1a44e
trivy-config-scan-image-composer-tool
496 Bytes
sha256:ff432ab1e40e8c4c7e3c946054038dc83c9b03c94b43e44297f821d81e755d9e
trivy-fs-scan-report-image-composer-tool
1.29 KB
sha256:4ba4bf9ea07dd4e3345266d55f480f7b9cbb6e3dfbb6dee91b463aee839cb717
zizmor-scan-report-image-composer-tool
594 Bytes
sha256:97185275306b9b4cda0fc58471dcb06c3e82bd530df1018aee89614fc293cefd