Skip to content

Destroy Expired Environment #690

Destroy Expired Environment

Destroy Expired Environment #690

Triggered via schedule April 16, 2026 00:51
Status Success
Total duration 7m 54s
Artifacts
envs_to_destroy
3m 49s
envs_to_destroy
Matrix: destroy_environment
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
envs_to_destroy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, aws-actions/configure-aws-credentials@5fd3084fc36e372ff1fff382a39b10d03659f355. 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/
destroy_environment (dg-demo, production-cft) / Destroy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, aws-actions/configure-aws-credentials@5fd3084fc36e372ff1fff382a39b10d03659f355, azure/login@a457da9ea143d694b1b9c7c869ebb04ebe844ef5, google-github-actions/auth@c200f3691d83b41bf9bbd8638997a462592937ed, hashicorp/vault-action@9c2d817b85b9fff56bcab21cb74b485aee9e9d73, slackapi/slack-github-action@e28cf165c92ffef168d23c5c9000cffc8a25e117. 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/
destroy_environment (proj-main-15apr0440, production-cft) / Destroy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, aws-actions/configure-aws-credentials@5fd3084fc36e372ff1fff382a39b10d03659f355, azure/login@a457da9ea143d694b1b9c7c869ebb04ebe844ef5, google-github-actions/auth@c200f3691d83b41bf9bbd8638997a462592937ed, hashicorp/vault-action@9c2d817b85b9fff56bcab21cb74b485aee9e9d73, slackapi/slack-github-action@e28cf165c92ffef168d23c5c9000cffc8a25e117. 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/