Fiz Zizmor issues #3552
garylouglint-test-build-publish.yml
on: pull_request
post-merge
/
sanitize-project-folder
pre-merge
/
sanitize-project-folder
3s
Lint YAML
38s
Lint Helm Charts
46s
Lint Go
2m 33s
pre-merge
/
license-compliance-check
19s
Lint Dockerfiles
41s
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
9s
pre-merge
/
secrets-gitleaks-scan
22s
pre-merge
/
trivy-filesystem-scan
23s
pre-merge
/
trivy-critical-scan
24s
pre-merge
/
trivy-config-scan
19s
pre-merge
/
bandit
19s
Matrix: Build and publish containers
Test Go
11m 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
29 warnings
|
Version Check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Check License
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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. 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. 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. 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. 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. 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/
|
|
Lint YAML
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Lint Dockerfiles
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Lint Helm Charts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build and publish Helm charts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build and publish containers (componentStatus)
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/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Lint Go
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/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build and publish containers (tenancyAPIMapping)
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/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build and publish containers (tenancyDatamodel)
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/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build and publish containers (tokenFS)
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/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build and publish containers (authService)
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/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build and publish containers (squidProxy)
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/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build and publish containers (openAPIGenerator)
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/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build and publish containers (awsSmProxy)
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/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build and publish containers (certSynchronizer)
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/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build and publish containers (keycloakTenantController)
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/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build and publish containers (secretsConfig)
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/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build and publish containers (tenancyInit)
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/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build and publish containers (nexusAPIGateway)
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/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build and publish containers (tenancyManager)
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/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build and publish containers (nexusCompiler)
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/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Version Tag
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Test Go
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/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, step-security/harden-runner@6c439dc8bdf85cadbbce9ed30d1c7b959517bc49. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-6gt4p6-orch-utils
Expired
|
175 Bytes |
sha256:dda62d0d35c88b3e5e80daf946efe4a5cbd73211910845b33c13e2438469d376
|
|
|
trivy-config-scan-orch-utils
|
9.88 KB |
sha256:ec5405a63be978776fdc141e3269a7be80267001d75cd3d6d04f976c8b99505b
|
|
|
trivy-fs-scan-report-orch-utils
|
488 Bytes |
sha256:a71233f9d6cf10362f79a9236578161e43b5a6f0d6154e646e9d06aa3becc237
|
|
|
zizmor-scan-report-orch-utils
|
902 Bytes |
sha256:1322da15dc8096ed87228a1745f31fb94388fd4082bb029ebf1d0805ecd3901e
|
|