Skip to content

Change nightly status script to not depend on time (#1863) #3923

Change nightly status script to not depend on time (#1863)

Change nightly status script to not depend on time (#1863) #3923

Triggered via push June 3, 2026 16:46
Status Success
Total duration 4h 30m 54s
Artifacts 32
log-inputs
5s
log-inputs
Matrix: build_desktop
Matrix: build_tools
build-and-package-ios-tvos
36m 29s
build-and-package-ios-tvos
build-and-package-android
13m 39s
build-and-package-android
download-sdk-package
0s
download-sdk-package
Matrix: package_desktop
final-merge-packages
26m 20s
final-merge-packages
create-windows-only-package
16m 29s
create-windows-only-package
cleanup-packaging-artifacts
3s
cleanup-packaging-artifacts
trigger_integration_tests
31s
trigger_integration_tests
attempt-retry
0s
attempt-retry
Fit to window
Zoom out
Zoom in

Annotations

21 errors, 35 warnings, and 8 notices
build-tools-darwin
WARNING: Cache entry deserialization failed, entry ignored
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-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-darwin-arm64-Release-static-legacy
WARNING: Cache entry deserialization failed, entry ignored
build-and-package-ios-tvos
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-darwin
WARNING: Cache entry deserialization failed, entry ignored
package-windows-x86-Release-dynamic
Failed to load artifacts.
package-windows-x86-Release-static
Failed to load artifacts.
package-linux
Failed to load artifacts.
package-windows-x64-Release-static
Failed to load artifacts.
package-windows-x64-Release-dynamic
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@v3, actions/checkout@v3, actions/setup-python@v4, actions/upload-artifact@v4. 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@v3, actions/setup-python@v4, actions/upload-artifact@v4. 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@v3, actions/checkout@v3, actions/upload-artifact@v4. 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@v3, actions/checkout@v3, actions/setup-python@v4, actions/upload-artifact@v4, nick-invision/retry@v2. 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@v3, actions/checkout@v3, actions/setup-python@v4, actions/upload-artifact@v4, nick-invision/retry@v2. 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@v3, actions/checkout@v3, actions/setup-python@v4, actions/upload-artifact@v4, nick-invision/retry@v2. 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@v3, actions/checkout@v3, actions/setup-python@v4, actions/upload-artifact@v4, nick-invision/retry@v2. 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@v3, actions/checkout@v3, actions/setup-python@v4, actions/upload-artifact@v4, nick-invision/retry@v2. 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@v3, actions/checkout@v3, actions/setup-python@v4, actions/upload-artifact@v4, nick-invision/retry@v2. 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@v3, actions/setup-python@v4, actions/upload-artifact@v4. 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@v3, actions/checkout@v3, actions/setup-python@v4, actions/upload-artifact@v4, microsoft/setup-msbuild@v1.1, nick-invision/retry@v2. 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@v3, actions/checkout@v3, actions/setup-python@v4, actions/upload-artifact@v4, microsoft/setup-msbuild@v1.1, nick-invision/retry@v2. 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@v3, actions/checkout@v3, actions/setup-python@v4, actions/upload-artifact@v4, microsoft/setup-msbuild@v1.1, nick-invision/retry@v2. 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@v3, actions/checkout@v3, actions/setup-python@v4, actions/upload-artifact@v4, microsoft/setup-msbuild@v1.1, nick-invision/retry@v2. 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@v3, actions/checkout@v3, actions/setup-python@v4, actions/upload-artifact@v4, microsoft/setup-msbuild@v1.1, nick-invision/retry@v2. 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@v3, actions/checkout@v3, actions/setup-python@v4, actions/upload-artifact@v4, microsoft/setup-msbuild@v1.1, nick-invision/retry@v2. 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@v3, actions/checkout@v3, actions/setup-python@v4, actions/upload-artifact@v4, microsoft/setup-msbuild@v1.1, nick-invision/retry@v2. 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@v3, actions/checkout@v3, actions/setup-python@v4, actions/upload-artifact@v4, microsoft/setup-msbuild@v1.1, nick-invision/retry@v2. 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@v3, actions/download-artifact@v4, actions/setup-python@v4, actions/upload-artifact@v4, geekyeggo/delete-artifact@v2. 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@v3, actions/download-artifact@v4, actions/setup-python@v4, actions/upload-artifact@v4, geekyeggo/delete-artifact@v2. 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@v3, actions/download-artifact@v4, actions/setup-python@v4, actions/upload-artifact@v4, geekyeggo/delete-artifact@v2. 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@v3, actions/download-artifact@v4, actions/setup-python@v4, actions/upload-artifact@v4, geekyeggo/delete-artifact@v2. 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@v3, actions/download-artifact@v4, actions/setup-python@v4, actions/upload-artifact@v4, geekyeggo/delete-artifact@v2. 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@v3, actions/download-artifact@v4, actions/setup-python@v4, actions/upload-artifact@v4, geekyeggo/delete-artifact@v2. 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@v3, actions/download-artifact@v4, actions/setup-python@v4, actions/upload-artifact@v4, geekyeggo/delete-artifact@v2. 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@v3, actions/download-artifact@v4, actions/setup-python@v4, actions/upload-artifact@v4, geekyeggo/delete-artifact@v2. 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@v3, actions/download-artifact@v4, actions/setup-python@v4, actions/upload-artifact@v4, geekyeggo/delete-artifact@v2. 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@v3, actions/download-artifact@v4, actions/setup-python@v4, actions/upload-artifact@v4, geekyeggo/delete-artifact@v2. 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@v3, actions/download-artifact@v4, actions/upload-artifact@v4. 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) = 1e8bfc5fc9d8ae28ed8bc64c7f2d1c9e29302e74c82a6e8901571d1771840e5e
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@v2. 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@v4, actions/upload-artifact@v4. 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) = 1066419bcdb90b9138021b3a1cec56e9a55e6920099171cdc2def11f9c2969c4
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@v3, actions/setup-python@v4, tibdex/github-app-token@v1. 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
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
build-windows-x64-Debug-dynamic-legacy
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
build-windows-x86-Debug-dynamic-legacy
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
build-windows-x86-Release-dynamic-legacy
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
build-windows-x86-Debug-static-legacy
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
build-windows-x64-Release-dynamic-legacy
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
build-windows-x86-Release-static-legacy
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
build-windows-x64-Release-static-legacy
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

Artifacts

Produced during runtime
Name Size Digest
firebase-cpp-sdk-android-package
71 MB
sha256:739435cce6d5d178ea6b3233d7b7ffdbe8685dbf19f0af267d5b12ca8635e39f
firebase-cpp-sdk-darwin-arm64-Release-static-legacy-build
365 MB
sha256:3b46e7600d12e7a68e6ac4bcc7cd39e7340b4e2f3f386545d0b2b7540f1afcaa
firebase-cpp-sdk-darwin-package
133 MB
sha256:a40581b9e7d60dc6114cdc62ece41cfe45229320fbed05a3fe853d87e971d3e4
firebase-cpp-sdk-darwin-x64-Release-static-legacy-build
366 MB
sha256:be3530541d8e2f8f7672cf941c6fe8c698f27f21faecd50781497f4bbf779520
firebase-cpp-sdk-ios-tvos-package
565 MB
sha256:e819b22922e963c37a821ff3d30b09ea40e94b25b6e47f449bdfac29dc234b0a
firebase-cpp-sdk-linux-package
86.8 MB
sha256:f482998478816f5331842c397b91db6b2c956ce0114dd0a84f42e3b717e299e8
firebase-cpp-sdk-linux-x64-Release-static-c++11-build
377 MB
sha256:77fe824d3987bf9dd61c8d194b6230515f3b656416900380e231e8baaa81a631
firebase-cpp-sdk-linux-x64-Release-static-legacy-build
376 MB
sha256:c9995d9fe97e796356087b07c0f40e51b5a61a13fbb86232fbd56b2e3e934458
firebase-cpp-sdk-linux-x86-Release-static-c++11-build
379 MB
sha256:33f579843de8be7056e0ae55b2206c15b9524ca80b483d1b2dc018290eaf477e
firebase-cpp-sdk-linux-x86-Release-static-legacy-build
377 MB
sha256:4080fc35a6e4991f2c393bc09964073f5daf0395098d136d02f58fcf62114e3c
firebase-cpp-sdk-windows-x64-Debug-dynamic-legacy-build
631 MB
sha256:e4e0a0deef0281cbac8440455210939797b66caed8bfb163b67372825700458b
firebase-cpp-sdk-windows-x64-Debug-dynamic-package
194 MB
sha256:9ad1e9f7934b6df2a19ddf5efa271a3a379d0f05af9b0ef5ee2afef2281cbe88
firebase-cpp-sdk-windows-x64-Debug-static-legacy-build
662 MB
sha256:eeb0699a198f6d4c042816e3e4f9a5a66f7b8692a960c60db2351b0b12982da8
firebase-cpp-sdk-windows-x64-Debug-static-package
218 MB
sha256:fc5446372955be59b5e0fa9e682fbacc7aea93170ef05ced4c144e270a829feb
firebase-cpp-sdk-windows-x64-Release-dynamic-legacy-build
355 MB
sha256:d0bec7fa7861b974f71473bc2702826c4d4d2a963024af81b2e77d82c94341b1
firebase-cpp-sdk-windows-x64-Release-dynamic-package
32 MB
sha256:1404200160abf48ff222107e42e9a1d062e49d227a8da634d9322a5aacdf9d7a
firebase-cpp-sdk-windows-x64-Release-static-legacy-build
363 MB
sha256:f4fcd7398c4e5dc92dd202ea0c0489a1050c9aca84d61b3ce47eb04da6af3789
firebase-cpp-sdk-windows-x64-Release-static-package
39.2 MB
sha256:7c60e24216b4b959adfb4d2177bbc0b3c31f27dda24e41070a11470e138207db
firebase-cpp-sdk-windows-x86-Debug-dynamic-legacy-build
593 MB
sha256:653f2c00794e160a057947c3e5f0ab2e0a4d1b8f6ff696eb7827c25d757e6816
firebase-cpp-sdk-windows-x86-Debug-dynamic-package
177 MB
sha256:68f81a8cce44a00d92636e8da4abd29f8ec7284ddb68dd5f0006b357be241157
firebase-cpp-sdk-windows-x86-Debug-static-legacy-build
613 MB
sha256:59745024b4d02154d1157d8f5b9e78d894991895126095976421bb7b196fea9d
firebase-cpp-sdk-windows-x86-Debug-static-package
197 MB
sha256:25f5340331e4ea83fd7084ac9110de92caa6e55f844d51d83ff176d58e4750a1
firebase-cpp-sdk-windows-x86-Release-dynamic-legacy-build
343 MB
sha256:f43a5b38047056f83aee2c9c630b2fa408158aa0dc6114f5fb6a87f79be5cfa1
firebase-cpp-sdk-windows-x86-Release-dynamic-package
25.7 MB
sha256:133c375f9e12ffa686659c6648663aad8dd9352d0e7136a061a7d98f58648825
firebase-cpp-sdk-windows-x86-Release-static-legacy-build
349 MB
sha256:6dbd41030c8064301cacfa3a6efbb2ba1694735ad60a42972b4144fee3dfb07b
firebase-cpp-sdk-windows-x86-Release-static-package
31 MB
sha256:b146884bec36c55226d2953f3fa89625bec1f77f144aaa854f2621c69b313f86
firebase_cpp_sdk.zip
1.71 GB
sha256:b59e49180a465cb039c1e2abf0c3e5f4f4622aeefe6a20d6a71bceb03865f946
firebase_cpp_sdk_hash.txt
257 Bytes
sha256:4c011fe2563287acea1af0e7b6c79ee7a22379b5a9564c267619fc6a23b88f7b
firebase_cpp_sdk_windows.zip
901 MB
sha256:7c088e85d679c0b68750956776bac937fe0e8c9820a2844bb4ece2c8f2132ffa
firebase_cpp_sdk_windows_hash.txt
279 Bytes
sha256:ef1626ac1a64aa74393318f46b18a78cbbcc033568610c68447c89a7bff8e61f
packaging-tools-darwin
45.9 MB
sha256:66bbd9532b5e6d297237904d8463dad0fc60026ade8e6ea178221efc22297464
packaging-tools-linux
266 MB
sha256:a59fd95aefe6348d7c00eb65a517be8ddfa04e231099c97ffdb99e7bc8cf6d65