Dockerfile: Bump golang from fcdb3e4 to 5f3787b in /auth-service
#3893
paladelint-test-build-publish.yml
on: pull_request
post-merge
/
sanitize-project-folder
pre-merge
/
sanitize-project-folder
2s
Lint YAML
39s
Lint Helm Charts
54s
Lint Go
2m 9s
pre-merge
/
license-compliance-check
15s
Lint Dockerfiles
46s
post-merge
/
version-bump
post-merge
/
bandit
post-merge
/
secrets-gitleaks-scan
post-merge
/
trivy-config-scan
post-merge
/
trivy-filesystem-scan
post-merge
/
zizmor-scan
pre-merge
/
zizmor-scan
11s
pre-merge
/
secrets-gitleaks-scan
22s
pre-merge
/
trivy-filesystem-scan
18s
pre-merge
/
trivy-critical-scan
25s
pre-merge
/
trivy-config-scan
19s
pre-merge
/
bandit
25s
Matrix: Build and publish containers
Test Go
12m 36s
post-merge
/
...
/
notify
Matrix: post-merge / sign-binaries
Waiting for pending jobs
Matrix: post-merge / sign-images
Waiting for pending jobs
Matrix: post-merge / scan-images
Waiting for pending jobs
Matrix: pre-merge / Scan Docker Images for CIS
Version Tag
37s
Annotations
5 warnings
|
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 / 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/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, tj-actions/changed-files@ed68ef82c095e0d48ec87eccea555d944a631a4c. 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 / bandit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065, tj-actions/changed-files@823fcebdb31bb35fdf2229d9f769b400309430d0. 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-cjzevt-orch-utils
|
175 Bytes |
sha256:4d6b67dc61711e3da6583235d7e3b79c89ed2c1f7f5517fd590bc90fc38c32f3
|
|
|
trivy-config-scan-orch-utils
|
9.87 KB |
sha256:a0771cffb4e6946a15fb898b57286fb6942988cad25cd7bce86eb2eda8fe145c
|
|
|
trivy-fs-scan-report-orch-utils
|
489 Bytes |
sha256:011f807fd7f69a4f0741b1cacd54b482916696d4398544898c664b8f91b09e9f
|
|
|
zizmor-scan-report-orch-utils
|
1.19 KB |
sha256:c2a4a036de1eab6d7fa2a34a5d782442f832c8842a7492848503eeb863f0697c
|
|