Merge pull request #256 from dynamsoft-docs/preview #494
main.yml
on: push
Update-BBS-On-Preview-Change
/
Build-Site-Preview
Update-DBR-Core-On-Preview-Change
/
Build-Site-Preview
Update-DBR-Js-On-Preview-Change
/
Build-Site-Preview
Update-DBR-Mobile-On-Preview-Change
/
Build-Site-Preview
Update-DBR-Server-On-Preview-Change
/
Build-Site-Preview
Update-DCE-Core-On-Preview-Change
/
Build-Site-Preview
Update-DCE-JS-On-Preview-Change
/
Build-Site-Preview
Update-DCE-Mobile-On-Preview-Change
/
Build-Site-Preview
Update-DCP-Core-On-Preview-Change
/
Build-Site-Preview
Update-DCP-Js-On-Preview-Change
/
Build-Site-Preview
Update-DCP-Mobile-On-Preview-Change
/
Build-Site-Preview
Update-DCP-Server-On-Preview-Change
/
Build-Site-Preview
Update-DCV-Core-On-Preview-Change
/
Build-Site-Preview
Update-DCV-Js-On-Preview-Change
/
Build-Site-Preview
Update-DCV-Mobile-On-Preview-Change
/
Build-Site-Preview
Update-DCV-Server-On-Preview-Change
/
Build-Site-Preview
Update-DDN-Core-On-Preview-Change
/
Build-Site-Preview
Update-DDN-Js-On-Preview-Change
/
Build-Site-Preview
Update-DDN-Mobile-On-Preview-Change
/
Build-Site-Preview
Update-DDN-Server-On-Preview-Change
/
Build-Site-Preview
Update-DDV-On-Preview-Change
/
Build-Site-Preview
Update-DLR-Core-On-Preview-Change
/
Build-Site-Preview
Update-DLR-Js-On-Preview-Change
/
Build-Site-Preview
Update-DLR-Mobile-On-Preview-Change
/
Build-Site-Preview
Update-DLR-Server-On-Preview-Change
/
Build-Site-Preview
Update-DWT-On-Preview-Change
/
Build-Site-Preview
Update-MDS-On-Preview-Change
/
Build-Site-Preview
Update-MRZ-Core-On-Preview-Change
/
Build-Site-Preview
Update-MRZ-Js-On-Preview-Change
/
Build-Site-Preview
Update-MRZ-Mobile-On-Preview-Change
/
Build-Site-Preview
Update-MWC-On-Preview-Change
/
Build-Site-Preview
Update-DBR-Core-On-Main-Change
/
Build-And-Sync-To-Production
16s
Update-DBR-Server-On-Main-Change
/
Build-And-Sync-To-Production
22s
Update-DBR-Mobile-On-Main-Change
/
Build-And-Sync-To-Production
22s
Update-DBR-Js-On-Main-Change
/
Build-And-Sync-To-Production
13s
Update-DCV-Core-On-Main-Change
/
Build-And-Sync-To-Production
22s
Update-DCV-Server-On-Main-Change
/
Build-And-Sync-To-Production
31s
Update-DCV-Mobile-On-Main-Change
/
Build-And-Sync-To-Production
29s
Update-DCV-Js-On-Main-Change
/
Build-And-Sync-To-Production
17s
Update-DLR-Core-On-Main-Change
/
Build-And-Sync-To-Production
13s
Update-DLR-Server-On-Main-Change
/
Build-And-Sync-To-Production
14s
Update-DLR-Mobile-On-Main-Change
/
Build-And-Sync-To-Production
13s
Update-DLR-Js-On-Main-Change
/
Build-And-Sync-To-Production
13s
Update-DDN-Core-On-Main-Change
/
Build-And-Sync-To-Production
11s
Update-DDN-Server-On-Main-Change
/
Build-And-Sync-To-Production
13s
Update-DDN-Mobile-On-Main-Change
/
Build-And-Sync-To-Production
17s
Update-DDN-Js-On-Main-Change
/
Build-And-Sync-To-Production
13s
Update-DCP-Core-On-Main-Change
/
Build-And-Sync-To-Production
14s
Update-DCP-Server-On-Main-Change
/
Build-And-Sync-To-Production
13s
Update-DCP-Mobile-On-Main-Change
/
Build-And-Sync-To-Production
13s
Update-DCP-Js-On-Main-Change
/
Build-And-Sync-To-Production
15s
Update-DCE-Core-On-Main-Change
/
Build-And-Sync-To-Production
13s
Update-DCE-Mobile-On-Main-Change
/
Build-And-Sync-To-Production
17s
Update-DCE-JS-On-Main-Change
/
Build-And-Sync-To-Production
13s
Update-DWT-On-Main-Change
/
Build-And-Sync-To-Production
47s
Update-DDV-On-Main-Change
/
Build-And-Sync-To-Production
28s
Update-MWC-On-Main-Change
/
Build-And-Sync-To-Production
13s
Update-DLS-On-Main-Change
/
Build-And-Sync-To-Production
11s
Update-MRZ-Core-On-Main-Change
/
Build-And-Sync-To-Production
9s
Update-MRZ-Mobile-On-Main-Change
/
Build-And-Sync-To-Production
13s
Update-MRZ-Js-On-Main-Change
/
Build-And-Sync-To-Production
11s
Update-BBS-On-Main-Change
/
Build-And-Sync-To-Production
13s
Update-MDS-On-Main-Change
/
Build-And-Sync-To-Production
14s
Update-BBS-On-Preview-Change
/
Sync-To-Testing
Update-DBR-Core-On-Preview-Change
/
Sync-To-Testing
Update-DBR-Js-On-Preview-Change
/
Sync-To-Testing
Update-DBR-Mobile-On-Preview-Change
/
Sync-To-Testing
Update-DBR-Server-On-Preview-Change
/
Sync-To-Testing
Update-DCE-Core-On-Preview-Change
/
Sync-To-Testing
Update-DCE-JS-On-Preview-Change
/
Sync-To-Testing
Update-DCE-Mobile-On-Preview-Change
/
Sync-To-Testing
Update-DCP-Core-On-Preview-Change
/
Sync-To-Testing
Update-DCP-Js-On-Preview-Change
/
Sync-To-Testing
Update-DCP-Mobile-On-Preview-Change
/
Sync-To-Testing
Update-DCP-Server-On-Preview-Change
/
Sync-To-Testing
Update-DCV-Core-On-Preview-Change
/
Sync-To-Testing
Update-DCV-Js-On-Preview-Change
/
Sync-To-Testing
Update-DCV-Mobile-On-Preview-Change
/
Sync-To-Testing
Update-DCV-Server-On-Preview-Change
/
Sync-To-Testing
Update-DDN-Core-On-Preview-Change
/
Sync-To-Testing
Update-DDN-Js-On-Preview-Change
/
Sync-To-Testing
Update-DDN-Mobile-On-Preview-Change
/
Sync-To-Testing
Update-DDN-Server-On-Preview-Change
/
Sync-To-Testing
Update-DDV-On-Preview-Change
/
Sync-To-Testing
Update-DLR-Core-On-Preview-Change
/
Sync-To-Testing
Update-DLR-Js-On-Preview-Change
/
Sync-To-Testing
Update-DLR-Mobile-On-Preview-Change
/
Sync-To-Testing
Update-DLR-Server-On-Preview-Change
/
Sync-To-Testing
Update-DWT-On-Preview-Change
/
Sync-To-Testing
Update-MDS-On-Preview-Change
/
Sync-To-Testing
Update-MRZ-Core-On-Preview-Change
/
Sync-To-Testing
Update-MRZ-Js-On-Preview-Change
/
Sync-To-Testing
Update-MRZ-Mobile-On-Preview-Change
/
Sync-To-Testing
Update-MWC-On-Preview-Change
/
Sync-To-Testing
Annotations
32 warnings
|
Update-DBR-Js-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DCV-Server-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DBR-Core-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DBR-Server-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DLR-Server-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DCV-Core-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DCV-Mobile-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DLR-Core-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DBR-Mobile-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-MRZ-Js-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DCE-JS-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-MRZ-Mobile-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DCV-Js-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DCP-Js-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DLR-Js-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DDN-Mobile-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DCP-Server-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DCE-Core-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DDN-Js-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-MDS-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-MWC-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-BBS-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DLS-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DCP-Mobile-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DCE-Mobile-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DWT-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DLR-Mobile-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DDN-Core-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DCP-Core-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DDV-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-MRZ-Core-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Update-DDN-Server-On-Main-Change / Build-And-Sync-To-Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SamKirkland/FTP-Deploy-Action@4.3.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|