Skip to content

Fix Actions issues (#1867) #3938

Fix Actions issues (#1867)

Fix Actions issues (#1867) #3938

Triggered via push June 15, 2026 17:54
Status Success
Total duration 4h 23m 11s
Artifacts 32
log-inputs
3s
log-inputs
Matrix: build_desktop
Matrix: build_tools
build-and-package-ios-tvos
31m 43s
build-and-package-ios-tvos
build-and-package-android
14m 2s
build-and-package-android
download-sdk-package
download-sdk-package
Matrix: package_desktop
final-merge-packages
24m 39s
final-merge-packages
create-windows-only-package
16m 5s
create-windows-only-package
cleanup-packaging-artifacts
4s
cleanup-packaging-artifacts
trigger_integration_tests
34s
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-arm64-Release-static-legacy
WARNING: Cache entry deserialization failed, entry ignored
build-darwin-x64-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-static
Failed to load artifacts.
package-windows-x86-Release-dynamic
Failed to load artifacts.
package-linux
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-dynamic
Failed to load artifacts.
package-windows-x64-Debug-static
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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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/
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-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-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-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-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-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/
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) = fcb006688cee53c6f45e504da2d360ff88488aff5789ef15556aaa8d7a3e9e3f
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) = e819e03b3b6d3d39fffdd1c6dcf16ad7c6709311b646887fd31c946aad5ff4c5
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:3e09593498fd1d8f70b20895b76638e497437c7b4398079bcf9aa1c353df7763
firebase-cpp-sdk-darwin-arm64-Release-static-legacy-build
365 MB
sha256:eee6cd4ad02ddda5ee7757608afbff907ce09c1a6a9b8b7f8a79b062ea31026a
firebase-cpp-sdk-darwin-package
133 MB
sha256:70c911b49a8e42713667f62d382af7c9ff5681e2a8497f7986b6031de35518f8
firebase-cpp-sdk-darwin-x64-Release-static-legacy-build
366 MB
sha256:7b67c5ee8df419609e6ef17d794ecef4392a0ff1e50fc0ebcf85084851c33935
firebase-cpp-sdk-ios-tvos-package
565 MB
sha256:05571c65298b1ce2f671fbb0322b20a809043209d9f5b29364c926e26184eae1
firebase-cpp-sdk-linux-package
86.8 MB
sha256:e8637ce5e9316418c4d31583465b28f778fb39f94b92a6e209a1a518d61f67a5
firebase-cpp-sdk-linux-x64-Release-static-c++11-build
377 MB
sha256:df13a698ce9d21468dcd879f889e1da844dc980db2d93623aa6e767865f6b14f
firebase-cpp-sdk-linux-x64-Release-static-legacy-build
376 MB
sha256:d5e48a7f077c84be433f97ffe5ac11a8017c50bfc7a35a210f864f25ead6c3a1
firebase-cpp-sdk-linux-x86-Release-static-c++11-build
379 MB
sha256:fc5c94fca1ebe9b7bfeedc0a0712ae26082e91ab6e169171f18e97e7de0bf202
firebase-cpp-sdk-linux-x86-Release-static-legacy-build
377 MB
sha256:4d1c30e8dd72cc4b7db6277a1858ea758d84a5abedebc4186c51e00b4eeba28e
firebase-cpp-sdk-windows-x64-Debug-dynamic-legacy-build
632 MB
sha256:61ab02b58db848e29a7fe7a9cc93a9f83f4caf6653c930f13bf133e49de75fe7
firebase-cpp-sdk-windows-x64-Debug-dynamic-package
194 MB
sha256:17e7276f8f29b4f2dbb6c588bcfd2fb16d271f0926fe10e71be1c00c4cd2c3d1
firebase-cpp-sdk-windows-x64-Debug-static-legacy-build
662 MB
sha256:be02b1b18a5a1125a7e888b3f38bc6d63b85034ea610e8ec7fd58f71c9e9b4d0
firebase-cpp-sdk-windows-x64-Debug-static-package
218 MB
sha256:ada2c366608c55e7eb817e8a74accfa2ec6f3b042e27f77a4badedcc1c3ae06b
firebase-cpp-sdk-windows-x64-Release-dynamic-legacy-build
355 MB
sha256:8605e22b80e8f739224b4ee46c5370358a91fdcfafbe462084b5ae247be5f3ac
firebase-cpp-sdk-windows-x64-Release-dynamic-package
32 MB
sha256:c820b5868fa5c731264f07565922e5a919eb11755d78ff7f793084b3aaefec6f
firebase-cpp-sdk-windows-x64-Release-static-legacy-build
363 MB
sha256:728eefc9588b9f13956d960b0efa958162ba3b48b973ecf37a24e4112dda7866
firebase-cpp-sdk-windows-x64-Release-static-package
39.2 MB
sha256:dc67ec9084c9876527ac9c30f58040f2c4dbfa2264bbd6b649ad72da102c1dbb
firebase-cpp-sdk-windows-x86-Debug-dynamic-legacy-build
593 MB
sha256:1bde7c5b6656ec336c33df44cdb73bd3772b65c3c2f665e90141961b65420ec6
firebase-cpp-sdk-windows-x86-Debug-dynamic-package
177 MB
sha256:af4f899e3e4f7f8d90cc102b96696d0a17c4e77e72e3354bfae291e454b3b0d9
firebase-cpp-sdk-windows-x86-Debug-static-legacy-build
613 MB
sha256:b55778e75a323d3a78e9460cfa82fe28597d4ef7dcf9438f2a29eb7c48da3150
firebase-cpp-sdk-windows-x86-Debug-static-package
197 MB
sha256:3eb9ed55bda985f8fe22e65994ede4505b9749ded3f9a1697e6b5f0d395d1621
firebase-cpp-sdk-windows-x86-Release-dynamic-legacy-build
343 MB
sha256:6ce617bf921c8c311ed8103dda7880a9aab9a2be81ce75d41e296fe179002308
firebase-cpp-sdk-windows-x86-Release-dynamic-package
25.7 MB
sha256:8741d90e4c2d69383c8ff37aa435de3111a776fe86c1fac902227513df19779b
firebase-cpp-sdk-windows-x86-Release-static-legacy-build
349 MB
sha256:11ddeb93bed0a69e9d671952af0db2baeb0c9e27d8862bf68a53ebe552291e5f
firebase-cpp-sdk-windows-x86-Release-static-package
31 MB
sha256:5155f3cb6c3eba14f50ef643ab7b422cdcec91463cf0d74a195b0aa5f0a19304
firebase_cpp_sdk.zip
1.71 GB
sha256:afc0ced97ee53e16e9fdc39abf51e40d5e4d257b093bb166d6a9f41a54f6bbed
firebase_cpp_sdk_hash.txt
254 Bytes
sha256:6ecf220d1f78729a404d6110dc494ccc22754779a44e2aa4617b0302564d80d8
firebase_cpp_sdk_windows.zip
901 MB
sha256:da584149525e3aae6f11721ba4512f76321db2d0ac338b1a4c7d655306345950
firebase_cpp_sdk_windows_hash.txt
279 Bytes
sha256:2e3a96fb44fc9458d150e698c9a6eb1383f261a56050874bb87a16d8f72c35dc
packaging-tools-darwin
45.9 MB
sha256:3821ab756df48681d2471963cf8ad79d89683edacbdd8d6d4979892cf18abe41
packaging-tools-linux
266 MB
sha256:e855fae37338cfd4cbb2d650b5f790e810368a8b8ec89cdfae2eec0fc79e6b7f