Check for Update and Build Parallel #666
Annotations
4 errors, 14 warnings, and 12 notices
|
trigger_builds (x86-64)
The specified node version file at: /home/runner/work/glua.dev/glua.dev/home/runner/work/glua.dev/glua.dev/full_repo/web/.nvmrc does not exist
|
|
trigger_builds (prerelease)
The specified node version file at: /home/runner/work/glua.dev/glua.dev/home/runner/work/glua.dev/glua.dev/full_repo/web/.nvmrc does not exist
|
|
trigger_builds (public)
The specified node version file at: /home/runner/work/glua.dev/glua.dev/home/runner/work/glua.dev/glua.dev/full_repo/web/.nvmrc does not exist
|
|
trigger_builds (dev)
The specified node version file at: /home/runner/work/glua.dev/glua.dev/home/runner/work/glua.dev/glua.dev/full_repo/web/.nvmrc does not exist
|
|
check_updates
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/
|
|
trigger_builds (x86-64)
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/setup-node@v4, docker/login-action@v3. 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/
|
|
trigger_builds (x86-64)
Tagging this release as the latest!
|
|
trigger_builds (x86-64)
Tagging with parent minor version: 0.8
|
|
trigger_builds (prerelease)
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/setup-node@v4, docker/login-action@v3. 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/
|
|
trigger_builds (prerelease)
Tagging this release as the latest!
|
|
trigger_builds (prerelease)
Tagging with parent minor version: 0.8
|
|
trigger_builds (public)
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/setup-node@v4, docker/login-action@v3. 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/
|
|
trigger_builds (public)
Tagging this release as the latest!
|
|
trigger_builds (public)
Tagging with parent minor version: 0.8
|
|
trigger_builds (dev)
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/setup-node@v4, docker/login-action@v3. 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/
|
|
trigger_builds (dev)
Tagging this release as the latest!
|
|
trigger_builds (dev)
Tagging with parent minor version: 0.8
|
|
update_last_versions
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/
|
|
trigger_builds (x86-64)
GHCR push took 79s
|
|
trigger_builds (x86-64)
Docker slim took 89s
|
|
trigger_builds (x86-64)
Docker build took 131s
|
|
trigger_builds (prerelease)
GHCR push took 77s
|
|
trigger_builds (prerelease)
Docker slim took 88s
|
|
trigger_builds (prerelease)
Docker build took 138s
|
|
trigger_builds (public)
GHCR push took 74s
|
|
trigger_builds (public)
Docker slim took 88s
|
|
trigger_builds (public)
Docker build took 144s
|
|
trigger_builds (dev)
GHCR push took 129s
|
|
trigger_builds (dev)
Docker slim took 91s
|
|
trigger_builds (dev)
Docker build took 116s
|