fix: optimized archive extraction path traversal checks #13
cyberchen1995Annotations
63 errors and 20 warnings
|
Publish Images (scratch, latest)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c CGO_ENABLED=0 GOOS=linux go build -ldflags \"-s -w -X 'main.version=${VERSION}-${TAG}' \" -o /app/***-cli main.go" did not complete successfully: exit code: 1
|
|
Publish Images (node:latest, node)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (node:16, node16)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (gradle:jdk8, gradle-jdk8)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (composer:latest, php)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (ruby:3.0, ruby3.0)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (maven:3-eclipse-temurin-8, maven3-jdk8)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (golang:1.18, go1.18)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (node:14, node14)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (golang:1.17, go1.17)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (python:latest, python)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (golang:1.12, go1.12)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (golang:latest, go)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (python:3.9, python3.9)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (golang:1.20, go1.20)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (golang:1.22, go1.22)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (python:3.11, python3.11)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (golang:1.21, go1.21)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (python:3.12, python3.12)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (python:3.8, python3.8)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (python:2.7, python2.7)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (erlang:latest, erlang)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (golang:1.14, go1.14)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (python:3.10, python3.10)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (rust:latest, rust)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (maven:latest, maven)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (maven:latest, maven)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c CGO_ENABLED=0 GOOS=linux go build -ldflags \"-s -w -X 'main.version=${VERSION}-${TAG}' \" -o /app/***-cli main.go" did not complete successfully: exit code: 1
|
|
Publish Images (gradle:jdk17, gradle-jdk17)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (gradle:jdk17, gradle-jdk17)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c CGO_ENABLED=0 GOOS=linux go build -ldflags \"-s -w -X 'main.version=${VERSION}-${TAG}' \" -o /app/***-cli main.go" did not complete successfully: exit code: 1
|
|
Publish Images (ruby:latest, ruby)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (ruby:latest, ruby)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c CGO_ENABLED=0 GOOS=linux go build -ldflags \"-s -w -X 'main.version=${VERSION}-${TAG}' \" -o /app/***-cli main.go" did not complete successfully: exit code: 1
|
|
Publish Images (maven:3-eclipse-temurin-21, maven3-jdk21)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (maven:3-eclipse-temurin-21, maven3-jdk21)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c CGO_ENABLED=0 GOOS=linux go build -ldflags \"-s -w -X 'main.version=${VERSION}-${TAG}' \" -o /app/***-cli main.go" did not complete successfully: exit code: 1
|
|
Publish Images (ruby:3.2, ruby3.2)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (ruby:3.2, ruby3.2)
The operation was canceled.
|
|
Publish Images (maven:3-eclipse-temurin-11, maven3-jdk11)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (maven:3-eclipse-temurin-11, maven3-jdk11)
The operation was canceled.
|
|
Publish Images (gradle:latest, gradle)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (gradle:latest, gradle)
The operation was canceled.
|
|
Publish Images (node:18, node18)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (node:18, node18)
The operation was canceled.
|
|
Publish Images (maven:3-eclipse-temurin-17, maven3-jdk17)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (maven:3-eclipse-temurin-17, maven3-jdk17)
The operation was canceled.
|
|
Publish Images (node:20, node20)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (node:20, node20)
The operation was canceled.
|
|
Publish Images (golang:1.15, go1.15)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (golang:1.15, go1.15)
The operation was canceled.
|
|
Publish Images (ruby:2.7, ruby2.7)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (ruby:2.7, ruby2.7)
The operation was canceled.
|
|
Publish Images (ruby:3.3, ruby3.3)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (ruby:3.3, ruby3.3)
The operation was canceled.
|
|
Publish Images (ruby:3.1, ruby3.1)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (ruby:3.1, ruby3.1)
The operation was canceled.
|
|
Publish Images (golang:1.19, go1.19)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (golang:1.16, go1.16)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (golang:1.19, go1.19)
The operation was canceled.
|
|
Publish Images (golang:1.16, go1.16)
The operation was canceled.
|
|
Publish Images (gradle:jdk11, gradle-jdk11)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (gradle:jdk11, gradle-jdk11)
The operation was canceled.
|
|
Publish Images (gradle:jdk21, gradle-jdk21)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (gradle:jdk21, gradle-jdk21)
The operation was canceled.
|
|
Publish Images (golang:1.13, go1.13)
The strategy configuration was canceled because "image-matrix.scratch_latest" failed
|
|
Publish Images (golang:1.13, go1.13)
The operation was canceled.
|
|
Publish Images (scratch, latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
|
|
Publish Images (maven:latest, maven)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
|
|
Publish Images (gradle:jdk17, gradle-jdk17)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
|
|
Publish Images (ruby:latest, ruby)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
|
|
Publish Images (maven:3-eclipse-temurin-21, maven3-jdk21)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
|
|
Publish Images (ruby:3.2, ruby3.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
|
|
Publish Images (maven:3-eclipse-temurin-11, maven3-jdk11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
|
|
Publish Images (gradle:latest, gradle)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
|
|
Publish Images (node:18, node18)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
|
|
Publish Images (maven:3-eclipse-temurin-17, maven3-jdk17)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
|
|
Publish Images (node:20, node20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
|
|
Publish Images (golang:1.15, go1.15)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
|
|
Publish Images (ruby:2.7, ruby2.7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
|
|
Publish Images (ruby:3.3, ruby3.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
|
|
Publish Images (ruby:3.1, ruby3.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
|
|
Publish Images (golang:1.19, go1.19)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
|
|
Publish Images (golang:1.16, go1.16)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
|
|
Publish Images (gradle:jdk11, gradle-jdk11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
|
|
Publish Images (gradle:jdk21, gradle-jdk21)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
|
|
Publish Images (golang:1.13, go1.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
|