Skip to content

Change it so that the header files are directly included (#1865) #3940

Change it so that the header files are directly included (#1865)

Change it so that the header files are directly included (#1865) #3940

Triggered via push June 16, 2026 13:56
Status Success
Total duration 4h 15m 13s
Artifacts 32
log-inputs
2s
log-inputs
Matrix: build_desktop
Matrix: build_tools
build-and-package-ios-tvos
29m 11s
build-and-package-ios-tvos
build-and-package-android
13m 46s
build-and-package-android
download-sdk-package
download-sdk-package
Matrix: package_desktop
final-merge-packages
17m 16s
final-merge-packages
create-windows-only-package
17m 27s
create-windows-only-package
cleanup-packaging-artifacts
3s
cleanup-packaging-artifacts
trigger_integration_tests
35s
trigger_integration_tests
attempt-retry
0s
attempt-retry
Fit to window
Zoom out
Zoom in

Annotations

16 errors and 53 warnings
build-tools-darwin
WARNING: Cache entry deserialization failed, entry ignored
build-darwin-x64-Release-static-legacy
WARNING: Cache entry deserialization failed, entry ignored
build-darwin-arm64-Release-static-legacy
WARNING: Cache entry deserialization failed, entry ignored
build-and-package-ios-tvos
WARNING: Cache entry deserialization failed, entry ignored
package-darwin
Failed to load artifacts.
package-darwin
WARNING: Cache entry deserialization failed, entry ignored
package-windows-x86-Release-dynamic
Failed to load artifacts.
package-linux
Failed to load artifacts.
package-windows-x86-Release-static
Failed to load artifacts.
package-windows-x64-Release-dynamic
Failed to load artifacts.
package-windows-x64-Release-static
Failed to load artifacts.
package-windows-x86-Debug-dynamic
Failed to load artifacts.
package-windows-x86-Debug-static
Failed to load artifacts.
package-windows-x64-Debug-static
Failed to load artifacts.
package-windows-x64-Debug-dynamic
Failed to load artifacts.
cleanup-packaging-artifacts
Failed to load artifacts.
build-tools-darwin
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
build-tools-linux
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
build-and-package-android
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
build-linux-x64-Release-static-c++11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, nick-invision/retry@14672906e672a08bd6eeb15720e9ed3ce869cdd4. 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/
build-darwin-x64-Release-static-legacy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, nick-invision/retry@14672906e672a08bd6eeb15720e9ed3ce869cdd4. 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/
build-darwin-x64-Release-static-legacy
The following taps are not trusted: aws/tap azure/bicep Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
build-darwin-x64-Release-static-legacy
The following taps are not trusted: aws/tap azure/bicep Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
build-darwin-x64-Release-static-legacy
The following taps are not trusted: aws/tap azure/bicep Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
build-darwin-x64-Release-static-legacy
The following taps are not trusted: aws/tap azure/bicep Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
build-darwin-x64-Release-static-legacy
The following taps are not trusted: aws/tap azure/bicep Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
build-darwin-arm64-Release-static-legacy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, nick-invision/retry@14672906e672a08bd6eeb15720e9ed3ce869cdd4. 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/
build-darwin-arm64-Release-static-legacy
The following taps are not trusted: aws/tap azure/bicep Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
build-darwin-arm64-Release-static-legacy
The following taps are not trusted: aws/tap azure/bicep Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
build-darwin-arm64-Release-static-legacy
The following taps are not trusted: aws/tap azure/bicep Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
build-darwin-arm64-Release-static-legacy
The following taps are not trusted: aws/tap azure/bicep Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
build-darwin-arm64-Release-static-legacy
The following taps are not trusted: aws/tap azure/bicep Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
build-linux-x86-Release-static-legacy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, nick-invision/retry@14672906e672a08bd6eeb15720e9ed3ce869cdd4. 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/
build-linux-x86-Release-static-c++11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, nick-invision/retry@14672906e672a08bd6eeb15720e9ed3ce869cdd4. 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/
build-linux-x64-Release-static-legacy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, nick-invision/retry@14672906e672a08bd6eeb15720e9ed3ce869cdd4. 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/
build-and-package-ios-tvos
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
build-windows-x86-Debug-static-legacy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, microsoft/setup-msbuild@34cfbaee7f672c76950673338facd8a73f637506, nick-invision/retry@14672906e672a08bd6eeb15720e9ed3ce869cdd4. 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/
build-windows-x64-Release-dynamic-legacy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, microsoft/setup-msbuild@34cfbaee7f672c76950673338facd8a73f637506, nick-invision/retry@14672906e672a08bd6eeb15720e9ed3ce869cdd4. 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/
build-windows-x86-Debug-dynamic-legacy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, microsoft/setup-msbuild@34cfbaee7f672c76950673338facd8a73f637506, nick-invision/retry@14672906e672a08bd6eeb15720e9ed3ce869cdd4. 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/
build-windows-x64-Debug-dynamic-legacy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, microsoft/setup-msbuild@34cfbaee7f672c76950673338facd8a73f637506, nick-invision/retry@14672906e672a08bd6eeb15720e9ed3ce869cdd4. 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/
build-windows-x64-Debug-static-legacy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, microsoft/setup-msbuild@34cfbaee7f672c76950673338facd8a73f637506, nick-invision/retry@14672906e672a08bd6eeb15720e9ed3ce869cdd4. 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/
build-windows-x86-Release-static-legacy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, microsoft/setup-msbuild@34cfbaee7f672c76950673338facd8a73f637506, nick-invision/retry@14672906e672a08bd6eeb15720e9ed3ce869cdd4. 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/
build-windows-x86-Release-dynamic-legacy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, microsoft/setup-msbuild@34cfbaee7f672c76950673338facd8a73f637506, nick-invision/retry@14672906e672a08bd6eeb15720e9ed3ce869cdd4. 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/
build-windows-x64-Release-static-legacy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c, actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, microsoft/setup-msbuild@34cfbaee7f672c76950673338facd8a73f637506, nick-invision/retry@14672906e672a08bd6eeb15720e9ed3ce869cdd4. 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/
package-darwin
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, geekyeggo/delete-artifact@54ab544f12cdb7b71613a16a2b5a37a9ade990af. 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/
package-darwin
The following taps are not trusted: aws/tap azure/bicep Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
package-darwin
The following taps are not trusted: aws/tap azure/bicep Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
package-darwin
The following taps are not trusted: aws/tap azure/bicep Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
package-darwin
The following taps are not trusted: aws/tap azure/bicep Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
package-darwin
The following taps are not trusted: aws/tap azure/bicep Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
package-darwin
The following taps are not trusted: aws/tap azure/bicep Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
package-windows-x86-Release-dynamic
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, geekyeggo/delete-artifact@54ab544f12cdb7b71613a16a2b5a37a9ade990af. 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/
package-linux
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, geekyeggo/delete-artifact@54ab544f12cdb7b71613a16a2b5a37a9ade990af. 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/
package-windows-x86-Release-static
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, geekyeggo/delete-artifact@54ab544f12cdb7b71613a16a2b5a37a9ade990af. 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/
package-windows-x64-Release-dynamic
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, geekyeggo/delete-artifact@54ab544f12cdb7b71613a16a2b5a37a9ade990af. 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/
package-windows-x64-Release-static
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, geekyeggo/delete-artifact@54ab544f12cdb7b71613a16a2b5a37a9ade990af. 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/
package-windows-x86-Debug-dynamic
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, geekyeggo/delete-artifact@54ab544f12cdb7b71613a16a2b5a37a9ade990af. 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/
package-windows-x86-Debug-static
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, geekyeggo/delete-artifact@54ab544f12cdb7b71613a16a2b5a37a9ade990af. 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/
package-windows-x64-Debug-static
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, geekyeggo/delete-artifact@54ab544f12cdb7b71613a16a2b5a37a9ade990af. 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/
package-windows-x64-Debug-dynamic
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, geekyeggo/delete-artifact@54ab544f12cdb7b71613a16a2b5a37a9ade990af. 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/
final-merge-packages
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
final-merge-packages
SHA256 (firebase_cpp_sdk.zip) = 1dae6193595ddf5f9d11bcedb868d907d65286f1945601433a8f0fd4ed52b173
cleanup-packaging-artifacts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: geekyeggo/delete-artifact@54ab544f12cdb7b71613a16a2b5a37a9ade990af. 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/
create-windows-only-package
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
create-windows-only-package
SHA256 (firebase_cpp_sdk_windows.zip) = 19ddc236e35847402a49151a31962ae1f3e0cbf9fcf26b77e067f720bd9cca23
trigger_integration_tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-python@7f4fc3e22c37d6ff65e88745f38bd3157c663f7c. 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/
trigger_integration_tests
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
trigger_integration_tests
Input 'app-id' has been deprecated with message: Use 'client-id' instead.

Artifacts

Produced during runtime
Name Size Digest
firebase-cpp-sdk-android-package
71 MB
sha256:1622e51bea7843da43a2a1defb0119e3ec7caeac5f2af50df9172885cc4cd134
firebase-cpp-sdk-darwin-arm64-Release-static-legacy-build
365 MB
sha256:bc0416cdeb2de2bff7f838b5b545c808065d8ea7d0985fc4b23f9fd16151c131
firebase-cpp-sdk-darwin-package
133 MB
sha256:8af10a1059dd429367592b0028b85d38924b96dba5d85c9e293bdb9d29816d32
firebase-cpp-sdk-darwin-x64-Release-static-legacy-build
366 MB
sha256:0958066f63a541cd14254fdbf8a76d6d5fcc8c20e6f1cff0e607c137dedee084
firebase-cpp-sdk-ios-tvos-package
565 MB
sha256:ab9455a95f9db3d4c1794a822197545ba6e6a6a5d2001df6796997ac4f98c53c
firebase-cpp-sdk-linux-package
86.8 MB
sha256:e8e9caf9d4516455861df63898b58b54a06e5c06d949250d18d14f55b0942c93
firebase-cpp-sdk-linux-x64-Release-static-c++11-build
377 MB
sha256:6145cee493a7897e16620aa2be5dea425e815b7d2426c1c5da1c472a31569b2d
firebase-cpp-sdk-linux-x64-Release-static-legacy-build
376 MB
sha256:f900192e74680f1aa2054e53322414787d92cbfc2266713819211739f46b1ed4
firebase-cpp-sdk-linux-x86-Release-static-c++11-build
379 MB
sha256:81e20b9b26fd5976202a9046193a6cfc1849fd5bd5c1dabd7d1d0e1d966f2862
firebase-cpp-sdk-linux-x86-Release-static-legacy-build
377 MB
sha256:e822f4b25792bf41af7969782c3e0ee86770cf7cf0a31a0ca84ec83f78777753
firebase-cpp-sdk-windows-x64-Debug-dynamic-legacy-build
632 MB
sha256:a897c310cc016a1005e997bbc6b638aea45930befc3f0159d2e13509eab722a1
firebase-cpp-sdk-windows-x64-Debug-dynamic-package
194 MB
sha256:31a56ec83fda2378b30a6f39af0d474a5265d9baae2c0ad551545665040c4dd0
firebase-cpp-sdk-windows-x64-Debug-static-legacy-build
662 MB
sha256:bd84be57069fa419d69df48ead88a4dad6f207d4af45205a77106e6f24209ac3
firebase-cpp-sdk-windows-x64-Debug-static-package
218 MB
sha256:7de6dc19262819f4566f2003f680b91638b87c7cc23e2e0d636f3a57d9d78fa5
firebase-cpp-sdk-windows-x64-Release-dynamic-legacy-build
355 MB
sha256:8e3d854e216fb67779ddab3173af775d338a462ace255b9a7ca1295c14e5f376
firebase-cpp-sdk-windows-x64-Release-dynamic-package
32 MB
sha256:651e58a686a991bafe9fac0e30030cfcf508a7371fe67500b6e808c008de4256
firebase-cpp-sdk-windows-x64-Release-static-legacy-build
363 MB
sha256:bc877b7473181de8e1570819e18a9963b54c3e019467d80e2a1c3da74c4ab3de
firebase-cpp-sdk-windows-x64-Release-static-package
39.2 MB
sha256:381e4d0710264b3110e3a75d29f6d46b16c8b718fd4128bd8d513f5b06223fa3
firebase-cpp-sdk-windows-x86-Debug-dynamic-legacy-build
593 MB
sha256:ae7f65cdecef8e1c99ceae84d00732b56334a685c2fafcdd739045f269cbc720
firebase-cpp-sdk-windows-x86-Debug-dynamic-package
177 MB
sha256:7aa6702b88d5103ccdb98352ad07adf2a15d44bcf42b4ebd2f3274d9126930f0
firebase-cpp-sdk-windows-x86-Debug-static-legacy-build
613 MB
sha256:88f6f2da4d7f07a849569b10b759529b622008a515dc6190b57b8fd6905300f8
firebase-cpp-sdk-windows-x86-Debug-static-package
197 MB
sha256:0935b5eee527de9596bfcb2e672338afa2c28d9692739c196850702113315122
firebase-cpp-sdk-windows-x86-Release-dynamic-legacy-build
343 MB
sha256:34a008f98100efba5fbdcdb62a75a4effc10c369f18ece9c825cc567b3571ca9
firebase-cpp-sdk-windows-x86-Release-dynamic-package
25.7 MB
sha256:2a6a11022d25e7dc5d47d5649c2c5ea0071f15bd72b9a8536b918cddbd5eb333
firebase-cpp-sdk-windows-x86-Release-static-legacy-build
349 MB
sha256:1ce428da98440fb6fe468b4cb316d38fdeaa5fcca4cfe98114ea5c1e1a40a0ba
firebase-cpp-sdk-windows-x86-Release-static-package
31 MB
sha256:6f5f9110942f741c9089ea3fc937de4ccfc14ecdb01515256443e8c95717e752
firebase_cpp_sdk.zip
1.71 GB
sha256:72c66e6ada8fbf41655ae2689ca53a75e7b66cbb38745c05128ff58940ce9243
firebase_cpp_sdk_hash.txt
257 Bytes
sha256:8fd2b132d25e29df8d3101e6db43bc02362807e7d39b85b1ef1eb312b76e43ab
firebase_cpp_sdk_windows.zip
901 MB
sha256:2a990998dc46c239e8295a0227d9ff4231fa43dc452a60bf2077ce241996b679
firebase_cpp_sdk_windows_hash.txt
281 Bytes
sha256:ce9d3c04d376e1098b7038d67ac615677cd18aa40a4a8b3b05ccaf783db277b8
packaging-tools-darwin
45.9 MB
sha256:061f7856dd08146a27ec56535232ebd1cb3cae4f186f736e40ac5b4e64e57d46
packaging-tools-linux
266 MB
sha256:5e4a01f78f5e4c6f183440a9f3722af016c2cdd4deffe30ffcb55facdcbd39ed