Process completed with exit code 1.

/datum/traitor_objective/locate_weakpoint failed to generate their objective. Reason: list index out of bounds code/modules/antagonists/traitor/objectives/locate_weakpoint.dm:66 proc name: generate objective (/datum/traitor_objective/locate_weakpoint/generate_objective) source file: code/modules/antagonists/traitor/objectives/locate_weakpoint.dm,66 usr: null src: Triangulate station\'s structu... (/datum/traitor_objective/locate_weakpoint) call stack: Triangulate station\'s structu... (/datum/traitor_objective/locate_weakpoint): generate objective(Johan Enderly (/datum/mind), /list (/list)) /datum/unit_test/traitor (/datum/unit_test/traitor): Run() RunUnitTest(/datum/unit_test/traitor (/datum/unit_test/traitor), /list (/list)) RunUnitTests() /datum/callback (/datum/callback): InvokeAsync()

/datum/traitor_objective/locate_weakpoint failed to generate their objective. Reason: list index out of bounds code/modules/antagonists/traitor/objectives/locate_weakpoint.dm:66 proc name: generate objective (/datum/traitor_objective/locate_weakpoint/generate_objective) source file: code/modules/antagonists/traitor/objectives/locate_weakpoint.dm,66 usr: null src: Triangulate station\'s structu... (/datum/traitor_objective/locate_weakpoint) call stack: Triangulate station\'s structu... (/datum/traitor_objective/locate_weakpoint): generate objective(Jennie Cook (/datum/mind), /list (/list)) /datum/unit_test/traitor (/datum/unit_test/traitor): Run() RunUnitTest(/datum/unit_test/traitor (/datum/unit_test/traitor), /list (/list)) RunUnitTests() /datum/callback (/datum/callback): InvokeAsync()

FAIL /datum/unit_test/spell_names 0s

Spell: Stop Time (/datum/action/cooldown/spell/timestop/sloth) had a name identical to another spell. This can cause confusion for admins giving out spells, and while debugging. Consider giving the name an adjective if it's a subtype. ("Greater", "Lesser", "Deadly".)

FAIL /datum/unit_test/missing_icons/worn_icons 0.6s

/obj/item/manual_cell_recharger using invalid icon_state, "handheldcharger_black_empty" in 'icons/mob/clothing/belt.dmi'

FAIL /datum/unit_test/crafting 10.9s

custom_materials of /obj/item/stake/hardened when crafted compared to only spawned don't match. should be: custom_materials = list(/datum/material/wood = SHEET_MATERIAL_AMOUNT * 3, /datum/material/iron = HALF_SHEET_MATERIAL_AMOUNT) (you can round a bit for values above 100) (current value: list(/datum/material/iron = HALF_SHEET_MATERIAL_AMOUNT)). Fix that. Otherwise, set the requirements_mats_blacklist or removed_mats var of /datum/crafting_recipe/hardened_stake, or add the CRAFT_SKIP_MATERIALS_PARITY crafting flag to it

FAIL /datum/unit_test/cargo_crate_sanity 6.1s

[19:27:25] Runtime in code/datums/components/stationloving.dm,62: Unable to find a blobstart landmark for /datum/component/stationloving to relocate the Archive of the Kindred. proc name: relocate (/datum/component/stationloving/proc/relocate) src: /datum/component/stationloving (/datum/component/stationloving) call stack: /datum/component/stationloving (/datum/component/stationloving): relocate() /datum/component/stationloving (/datum/component/stationloving): Initialize(0, 1) /datum/component/stationloving (/datum/component/stationloving): New(/list (/list)) the Archive of the Kindred (/obj/item/book/kindred): AddComponent(/list (/list), null) the Archive of the Kindred (/obj/item/book/kindred): Initialize(0) Atoms (/datum/controller/subsystem/atoms): InitAtom(the Archive of the Kindred (/obj/item/book/kindred), 0, /list (/list)) the Archive of the Kindred (/obj/item/book/kindred): New(0) the Codex Gigas (/obj/item/book/codex_gigas): Initialize(0) Atoms (/datum/controller/subsystem/atoms): InitAtom(the Codex Gigas (/obj/item/book/codex_gigas), 0, /list (/list)) the Codex Gigas (/obj/item/book/codex_gigas): New(0) Book Crate (/datum/supply_pack/misc/book_crate): fill(the crate (/obj/structure/closet/crate/wooden)) Book Crate (/datum/supply_pack/misc/book_crate): generate(the floor (126,126,7) (/turf/open/floor/iron), null) /datum/unit_test/cargo_crate_s... (/datum/unit_test/cargo_crate_sanity): Run() RunUnitTest(/datum/unit_test/cargo_crate_s... (/datum/unit_test/cargo_crate_sanity), /list (/list)) RunUnitTests() /datum/callback (/datum/callback): InvokeAsync()

/obj/machinery/light/directional/south Could not find attachable object at /area/station/construction (155,57,3)

The airlock unrestricted side helper failed to find an airlock at Icemoon Wastes (141,175,6)

The airlock abandoned helper failed to find an airlock at Icemoon Wastes (141,175,6)

The airlock abandoned helper failed to find an airlock at Departure Lounge (126,108,6)

/obj/structure/extinguisher_cabinet/directional/east Could not find attachable object at /area/station/maintenance/disposal/incinerator (93,132,5) (92,132,5)

/obj/item/radio/intercom/directional/east Could not find attachable object at /area/station/maintenance/disposal/incinerator (93,133,5) (92,133,5)

/obj/machinery/airalarm/directional/east Could not find attachable object at /area/station/maintenance/disposal/incinerator (93,136,5) (92,136,5)

/obj/machinery/light_switch/directional/north Could not find attachable object at /area/station/maintenance/disposal/incinerator (89,138,5) (89,137,5)

/obj/machinery/firealarm/directional/west Could not find attachable object at /area/station/maintenance/disposal/incinerator (85,134,5) (86,134,5)

/obj/machinery/power/apc/auto_name/directional/west Could not find attachable object at /area/station/maintenance/disposal/incinerator (85,136,5) (86,136,5)

/mob/living/silicon/ai/spawned didn't return an Initialize hint

/mob/living/silicon didn't return an Initialize hint

/mob/living/silicon/robot didn't return an Initialize hint

/mob/living/silicon/ai didn't return an Initialize hint

FAIL /datum/unit_test/spell_names 0s

Spell: Stop Time (/datum/action/cooldown/spell/timestop/sloth) had a name identical to another spell. This can cause confusion for admins giving out spells, and while debugging. Consider giving the name an adjective if it's a subtype. ("Greater", "Lesser", "Deadly".)

FAIL /datum/unit_test/missing_icons/worn_icons 0.6s

/obj/item/manual_cell_recharger using invalid icon_state, "handheldcharger_black_empty" in 'icons/mob/clothing/belt.dmi'

FAIL /datum/unit_test/crafting 10.5s

custom_materials of /obj/item/stake/hardened when crafted compared to only spawned don't match. should be: custom_materials = list(/datum/material/wood = SHEET_MATERIAL_AMOUNT * 3, /datum/material/iron = HALF_SHEET_MATERIAL_AMOUNT) (you can round a bit for values above 100) (current value: list(/datum/material/iron = HALF_SHEET_MATERIAL_AMOUNT)). Fix that. Otherwise, set the requirements_mats_blacklist or removed_mats var of /datum/crafting_recipe/hardened_stake, or add the CRAFT_SKIP_MATERIALS_PARITY crafting flag to it

/mob/living/silicon didn't return an Initialize hint

/mob/living/silicon/robot didn't return an Initialize hint

/mob/living/silicon/ai didn't return an Initialize hint

/mob/living/silicon/robot/shell/cell didn't return an Initialize hint

FAIL /datum/unit_test/spell_names 0s

Spell: Stop Time (/datum/action/cooldown/spell/timestop/sloth) had a name identical to another spell. This can cause confusion for admins giving out spells, and while debugging. Consider giving the name an adjective if it's a subtype. ("Greater", "Lesser", "Deadly".)

FAIL /datum/unit_test/missing_icons/worn_icons 0.6s

/obj/item/manual_cell_recharger using invalid icon_state, "handheldcharger_black_empty" in 'icons/mob/clothing/belt.dmi'

FAIL /datum/unit_test/crafting 7.8s

custom_materials of /obj/item/stake/hardened when crafted compared to only spawned don't match. should be: custom_materials = list(/datum/material/wood = SHEET_MATERIAL_AMOUNT * 3, /datum/material/iron = HALF_SHEET_MATERIAL_AMOUNT) (you can round a bit for values above 100) (current value: list(/datum/material/iron = HALF_SHEET_MATERIAL_AMOUNT)). Fix that. Otherwise, set the requirements_mats_blacklist or removed_mats var of /datum/crafting_recipe/hardened_stake, or add the CRAFT_SKIP_MATERIALS_PARITY crafting flag to it

/mob/living/silicon/ai/spawned didn't return an Initialize hint

/mob/living/silicon didn't return an Initialize hint

/mob/living/silicon/robot didn't return an Initialize hint

/mob/living/silicon/ai didn't return an Initialize hint

FAIL /datum/unit_test/spell_names 0s

Spell: Stop Time (/datum/action/cooldown/spell/timestop/sloth) had a name identical to another spell. This can cause confusion for admins giving out spells, and while debugging. Consider giving the name an adjective if it's a subtype. ("Greater", "Lesser", "Deadly".)

FAIL /datum/unit_test/missing_icons/worn_icons 0.7s

/obj/item/manual_cell_recharger using invalid icon_state, "handheldcharger_black_empty" in 'icons/mob/clothing/belt.dmi'

FAIL /datum/unit_test/crafting 11.2s

custom_materials of /obj/item/stake/hardened when crafted compared to only spawned don't match. should be: custom_materials = list(/datum/material/wood = SHEET_MATERIAL_AMOUNT * 3, /datum/material/iron = HALF_SHEET_MATERIAL_AMOUNT) (you can round a bit for values above 100) (current value: list(/datum/material/iron = HALF_SHEET_MATERIAL_AMOUNT)). Fix that. Otherwise, set the requirements_mats_blacklist or removed_mats var of /datum/crafting_recipe/hardened_stake, or add the CRAFT_SKIP_MATERIALS_PARITY crafting flag to it

/mob/living/silicon/ai/spawned didn't return an Initialize hint

/mob/living/silicon didn't return an Initialize hint

/mob/living/silicon/robot didn't return an Initialize hint

/mob/living/silicon/ai didn't return an Initialize hint

FAIL /datum/unit_test/spell_names 0s

Spell: Stop Time (/datum/action/cooldown/spell/timestop/sloth) had a name identical to another spell. This can cause confusion for admins giving out spells, and while debugging. Consider giving the name an adjective if it's a subtype. ("Greater", "Lesser", "Deadly".)

FAIL /datum/unit_test/missing_icons/worn_icons 0.6s

/obj/item/manual_cell_recharger using invalid icon_state, "handheldcharger_black_empty" in 'icons/mob/clothing/belt.dmi'

FAIL /datum/unit_test/crafting 10.8s

custom_materials of /obj/item/stake/hardened when crafted compared to only spawned don't match. should be: custom_materials = list(/datum/material/wood = SHEET_MATERIAL_AMOUNT * 3, /datum/material/iron = HALF_SHEET_MATERIAL_AMOUNT) (you can round a bit for values above 100) (current value: list(/datum/material/iron = HALF_SHEET_MATERIAL_AMOUNT)). Fix that. Otherwise, set the requirements_mats_blacklist or removed_mats var of /datum/crafting_recipe/hardened_stake, or add the CRAFT_SKIP_MATERIALS_PARITY crafting flag to it

custom_materials of /obj/item/stake/hardened when crafted compared to only spawned don't match. should be: custom_materials = list(/datum/material/wood = SHEET_MATERIAL_AMOUNT * 3, /datum/material/iron = HALF_SHEET_MATERIAL_AMOUNT) (you can round a bit for values above 100) (current value: list(/datum/material/iron = HALF_SHEET_MATERIAL_AMOUNT)). Fix that. Otherwise, set the requirements_mats_blacklist or removed_mats var of /datum/crafting_recipe/hardened_stake, or add the CRAFT_SKIP_MATERIALS_PARITY crafting flag to it

FAIL /datum/unit_test/maptest_log_mapping 0s

/obj/structure/sign/warning Could not find attachable object at /area/station/maintenance/department/science/central (175,137,2)

/obj/machinery/light/directional/south Could not find attachable object at /area/station/maintenance/disposal/incinerator (156,83,2)

/obj/machinery/light/directional/south Could not find attachable object at /area/station/maintenance/department/science/central (156,132,2)

/obj/machinery/light/small/directional/south Could not find attachable object at /area/station/commons/toilet/auxiliary (107,152,2)

/obj/machinery/light/directional/east Could not find attachable object at /area/station/medical/morgue (93,127,2)

/obj/machinery/camera/silicon Could not find attachable object at /area/station/ai/satellite/chamber (130,214,2)

/obj/machinery/camera/silicon Could not find attachable object at /area/station/ai/satellite/chamber (128,214,2)

Duplicate APC created at AI Satellite Exterior (135,205,2) /area/station/ai/satellite/exterior. Original at AI Satellite Exterior (122,197,2) /area/station/ai/satellite/exterior.

The external access at Port Solar Maintenance (124,117,4) failed to apply (cannot mix any/all access helpers: any existed, all failed)

The external access at Port Solar Maintenance (122,115,4) failed to apply (cannot mix any/all access helpers: any existed, all failed)

The tcoms access at Port Solar Maintenance (122,115,4) failed to apply (cannot mix any/all access helpers: any existed, all failed)

The minisat access at Telecomms Control Room (121,110,4) failed to apply (cannot mix any/all access helpers: all existed, any failed)

The external access at Port Solar Maintenance (121,114,4) failed to apply (cannot mix any/all access helpers: any existed, all failed)

The tcoms access at Port Solar Maintenance (121,114,4) failed to apply (cannot mix any/all access helpers: any existed, all failed)

The captain access at Captain's Quarters (128,150,3) failed to apply (cannot mix any/all access helpers: all existed, any failed)

The captain access at Captain's Quarters (126,148,3) failed to apply (cannot mix any/all access helpers: all existed, any failed)

The general access at Engineering Lobby (125,115,2) failed to apply (cannot mix any/all access helpers: all existed, any failed)

The general access at Construction Area (122,112,2) failed to apply (cannot mix any/all access helpers: all existed, any failed)

No fire alarm in region: Prisoner Education Chamber (57,94,2) (Region size: 19 turfs)

No fire alarm in region: Recreational Holodeck (55,114,2) (Region size: 128 turfs)

No fire alarm in region: Greater Port Maintenance (42,116,2) (Region size: 27 turfs)

No fire alarm in region: Greater Port Maintenance (44,116,2) (Region size: 18 turfs)

FAIL /datum/unit_test/spell_names 0s

Spell: Stop Time (/datum/action/cooldown/spell/timestop/sloth) had a name identical to another spell. This can cause confusion for admins giving out spells, and while debugging. Consider giving the name an adjective if it's a subtype. ("Greater", "Lesser", "Deadly".)

FAIL /datum/unit_test/missing_icons/worn_icons 0.6s

/obj/item/manual_cell_recharger using invalid icon_state, "handheldcharger_black_empty" in 'icons/mob/clothing/belt.dmi'

FAIL /datum/unit_test/crafting 10.9s

custom_materials of /obj/item/stake/hardened when crafted compared to only spawned don't match. should be: custom_materials = list(/datum/material/wood = SHEET_MATERIAL_AMOUNT * 3, /datum/material/iron = HALF_SHEET_MATERIAL_AMOUNT) (you can round a bit for values above 100) (current value: list(/datum/material/iron = HALF_SHEET_MATERIAL_AMOUNT)). Fix that. Otherwise, set the requirements_mats_blacklist or removed_mats var of /datum/crafting_recipe/hardened_stake, or add the CRAFT_SKIP_MATERIALS_PARITY crafting flag to it

/mob/living/silicon/ai/spawned didn't return an Initialize hint

/mob/living/silicon didn't return an Initialize hint

/mob/living/silicon/robot didn't return an Initialize hint

/mob/living/silicon/ai didn't return an Initialize hint

FAIL /datum/unit_test/spell_names 0s

Spell: Stop Time (/datum/action/cooldown/spell/timestop/sloth) had a name identical to another spell. This can cause confusion for admins giving out spells, and while debugging. Consider giving the name an adjective if it's a subtype. ("Greater", "Lesser", "Deadly".)

FAIL /datum/unit_test/missing_icons/worn_icons 0.6s

/obj/item/manual_cell_recharger using invalid icon_state, "handheldcharger_black_empty" in 'icons/mob/clothing/belt.dmi'

FAIL /datum/unit_test/crafting 10.3s

custom_materials of /obj/item/stake/hardened when crafted compared to only spawned don't match. should be: custom_materials = list(/datum/material/wood = SHEET_MATERIAL_AMOUNT * 3, /datum/material/iron = HALF_SHEET_MATERIAL_AMOUNT) (you can round a bit for values above 100) (current value: list(/datum/material/iron = HALF_SHEET_MATERIAL_AMOUNT)). Fix that. Otherwise, set the requirements_mats_blacklist or removed_mats var of /datum/crafting_recipe/hardened_stake, or add the CRAFT_SKIP_MATERIALS_PARITY crafting flag to it

/mob/living/silicon didn't return an Initialize hint

/mob/living/silicon/robot didn't return an Initialize hint

/mob/living/silicon/ai didn't return an Initialize hint

/mob/living/silicon/robot/shell/cell didn't return an Initialize hint

FAIL /datum/unit_test/spell_names 0s

Spell: Stop Time (/datum/action/cooldown/spell/timestop/sloth) had a name identical to another spell. This can cause confusion for admins giving out spells, and while debugging. Consider giving the name an adjective if it's a subtype. ("Greater", "Lesser", "Deadly".)

FAIL /datum/unit_test/missing_icons/worn_icons 0.5s

/obj/item/manual_cell_recharger using invalid icon_state, "handheldcharger_black_empty" in 'icons/mob/clothing/belt.dmi'

FAIL /datum/unit_test/crafting 10.8s

custom_materials of /obj/item/stake/hardened when crafted compared to only spawned don't match. should be: custom_materials = list(/datum/material/wood = SHEET_MATERIAL_AMOUNT * 3, /datum/material/iron = HALF_SHEET_MATERIAL_AMOUNT) (you can round a bit for values above 100) (current value: list(/datum/material/iron = HALF_SHEET_MATERIAL_AMOUNT)). Fix that. Otherwise, set the requirements_mats_blacklist or removed_mats var of /datum/crafting_recipe/hardened_stake, or add the CRAFT_SKIP_MATERIALS_PARITY crafting flag to it

Process completed with exit code 1.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@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/