Process completed with exit code 2.

use of undeclared identifier 'LUA_ERRGCMM'

The strategy configuration was canceled because "build-macos.macos-14_wo_maxmind_--wit" failed

The operation was canceled.

extraneous closing brace ('}')

The strategy configuration was canceled because "build-macos.macos-14_wo_maxmind_--wit" failed

The operation was canceled.

use of undeclared identifier 'LUA_ERRGCMM'

The strategy configuration was canceled because "build-macos.macos-14_wo_maxmind_--wit" failed

The operation was canceled.

The strategy configuration was canceled because "build-macos.macos-14_wo_maxmind_--wit" failed

The operation was canceled.

The strategy configuration was canceled because "build-macos.macos-14_wo_maxmind_--wit" failed

The operation was canceled.

The strategy configuration was canceled because "build-macos.macos-14_wo_maxmind_--wit" failed

The operation was canceled.

The strategy configuration was canceled because "build-macos.macos-14_wo_maxmind_--wit" failed

The operation was canceled.

The strategy configuration was canceled because "build-macos.macos-14_wo_maxmind_--wit" failed

The operation was canceled.

Process completed with exit code 2.

expected declaration before ‘}’ token

expected declaration before ‘}’ token

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

Process completed with exit code 2.

extraneous closing brace ('}')

extraneous closing brace ('}')

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

Process completed with exit code 2.

expected declaration before ‘}’ token

expected declaration before ‘}’ token

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

Process completed with exit code 2.

extraneous closing brace ('}')

extraneous closing brace ('}')

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

expected declaration before ‘}’ token

expected declaration before ‘}’ token

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

expected declaration before ‘}’ token

expected declaration before ‘}’ token

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

expected declaration before ‘}’ token

expected declaration before ‘}’ token

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

extraneous closing brace ('}')

extraneous closing brace ('}')

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

The strategy configuration was canceled because "build-linux.ubuntu-22_04_x64_amd64__5" failed

The operation was canceled.

'libinjection_xss': identifier not found [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

'{': missing function header (old-style formal list?) [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '{' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

'libinjection_sqli': identifier not found [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

'{': missing function header (old-style formal list?) [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '{' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

The strategy configuration was canceled because "build-windows.windows-2022_x64_x86_64_R" failed

'libinjection_sqli': identifier not found [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

'{': missing function header (old-style formal list?) [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '{' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

'libinjection_xss': identifier not found [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

'{': missing function header (old-style formal list?) [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '{' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

The strategy configuration was canceled because "build-windows.windows-2022_x64_x86_64_R" failed

'libinjection_xss': identifier not found [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

'{': missing function header (old-style formal list?) [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '{' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

'libinjection_sqli': identifier not found [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

'{': missing function header (old-style formal list?) [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '{' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

The strategy configuration was canceled because "build-windows.windows-2022_x64_x86_64_R" failed

'libinjection_xss': identifier not found [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

'{': missing function header (old-style formal list?) [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '{' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

'libinjection_sqli': identifier not found [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

'{': missing function header (old-style formal list?) [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '{' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

The strategy configuration was canceled because "build-windows.windows-2022_x64_x86_64_R" failed

'libinjection_sqli': identifier not found [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

'{': missing function header (old-style formal list?) [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '{' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

'libinjection_xss': identifier not found [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

'{': missing function header (old-style formal list?) [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '{' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

The strategy configuration was canceled because "build-windows.windows-2022_x64_x86_64_R" failed

'libinjection_xss': identifier not found [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

'{': missing function header (old-style formal list?) [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '{' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

'libinjection_sqli': identifier not found [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

'{': missing function header (old-style formal list?) [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '{' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: missing ';' before '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

syntax error: '}' [D:\a\ModSecurity\ModSecurity\build\win32\build\libModSecurity.vcxproj]

Process completed with exit code 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. 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/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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'fopen': This function or variable may be unsafe. Consider using fopen_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. [C:\Users\runneradmin\.conan2\p\b\poco4249bb087b8de\b\build\NetSSL_OpenSSL\NetSSL.vcxproj]

'argument': conversion from 'std::streamoff' to 'DWORD', possible loss of data [C:\Users\runneradmin\.conan2\p\b\poco4249bb087b8de\b\build\Net\Net.vcxproj]

'strncpy': This function or variable may be unsafe. Consider using strncpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. [C:\Users\runneradmin\.conan2\p\b\poco4249bb087b8de\b\build\Data\PostgreSQL\DataPostgreSQL.vcxproj]

'=': conversion from 'Poco::Int64' to 'long', possible loss of data [C:\Users\runneradmin\.conan2\p\b\poco4249bb087b8de\b\build\Data\PostgreSQL\DataPostgreSQL.vcxproj]

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/

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'fopen': This function or variable may be unsafe. Consider using fopen_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. [C:\Users\runneradmin\.conan2\p\b\pocob673885425c67\b\build\NetSSL_OpenSSL\NetSSL.vcxproj]

'argument': conversion from 'std::streamoff' to 'DWORD', possible loss of data [C:\Users\runneradmin\.conan2\p\b\pocob673885425c67\b\build\Net\Net.vcxproj]

'strncpy': This function or variable may be unsafe. Consider using strncpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. [C:\Users\runneradmin\.conan2\p\b\pocob673885425c67\b\build\Data\PostgreSQL\DataPostgreSQL.vcxproj]

'=': conversion from 'Poco::Int64' to 'long', possible loss of data [C:\Users\runneradmin\.conan2\p\b\pocob673885425c67\b\build\Data\PostgreSQL\DataPostgreSQL.vcxproj]

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/

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'fopen': This function or variable may be unsafe. Consider using fopen_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. [C:\Users\runneradmin\.conan2\p\b\poco499abb46ef226\b\build\NetSSL_OpenSSL\NetSSL.vcxproj]

'argument': conversion from 'std::streamoff' to 'DWORD', possible loss of data [C:\Users\runneradmin\.conan2\p\b\poco499abb46ef226\b\build\Net\Net.vcxproj]

'strncpy': This function or variable may be unsafe. Consider using strncpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. [C:\Users\runneradmin\.conan2\p\b\poco499abb46ef226\b\build\Data\PostgreSQL\DataPostgreSQL.vcxproj]

'=': conversion from 'Poco::Int64' to 'long', possible loss of data [C:\Users\runneradmin\.conan2\p\b\poco499abb46ef226\b\build\Data\PostgreSQL\DataPostgreSQL.vcxproj]

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/

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'fopen': This function or variable may be unsafe. Consider using fopen_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. [C:\Users\runneradmin\.conan2\p\b\poco360a148a326f7\b\build\NetSSL_OpenSSL\NetSSL.vcxproj]

'argument': conversion from 'std::streamoff' to 'DWORD', possible loss of data [C:\Users\runneradmin\.conan2\p\b\poco360a148a326f7\b\build\Net\Net.vcxproj]

'strncpy': This function or variable may be unsafe. Consider using strncpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. [C:\Users\runneradmin\.conan2\p\b\poco360a148a326f7\b\build\Data\PostgreSQL\DataPostgreSQL.vcxproj]

'=': conversion from 'Poco::Int64' to 'long', possible loss of data [C:\Users\runneradmin\.conan2\p\b\poco360a148a326f7\b\build\Data\PostgreSQL\DataPostgreSQL.vcxproj]

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/

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'fopen': This function or variable may be unsafe. Consider using fopen_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. [C:\Users\runneradmin\.conan2\p\b\pocod48a6562cfcad\b\build\NetSSL_OpenSSL\NetSSL.vcxproj]

'argument': conversion from 'std::streamoff' to 'DWORD', possible loss of data [C:\Users\runneradmin\.conan2\p\b\pocod48a6562cfcad\b\build\Net\Net.vcxproj]

'strncpy': This function or variable may be unsafe. Consider using strncpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. [C:\Users\runneradmin\.conan2\p\b\pocod48a6562cfcad\b\build\Data\PostgreSQL\DataPostgreSQL.vcxproj]

'=': conversion from 'Poco::Int64' to 'long', possible loss of data [C:\Users\runneradmin\.conan2\p\b\pocod48a6562cfcad\b\build\Data\PostgreSQL\DataPostgreSQL.vcxproj]

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/

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'=': incompatible types - from 'injection_result_t (__cdecl *)(h5_state_t *)' to 'ptr_html5_state' [D:\a\ModSecurity\ModSecurity\build\win32\build\libinjection.vcxproj]

'fopen': This function or variable may be unsafe. Consider using fopen_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. [C:\Users\runneradmin\.conan2\p\b\pocoba7acd860a656\b\build\NetSSL_OpenSSL\NetSSL.vcxproj]

'argument': conversion from 'std::streamoff' to 'DWORD', possible loss of data [C:\Users\runneradmin\.conan2\p\b\pocoba7acd860a656\b\build\Net\Net.vcxproj]

'strncpy': This function or variable may be unsafe. Consider using strncpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. [C:\Users\runneradmin\.conan2\p\b\pocoba7acd860a656\b\build\Data\PostgreSQL\DataPostgreSQL.vcxproj]

'=': conversion from 'Poco::Int64' to 'long', possible loss of data [C:\Users\runneradmin\.conan2\p\b\pocoba7acd860a656\b\build\Data\PostgreSQL\DataPostgreSQL.vcxproj]