CPP binary SDK packaging #3838
a-mauricecpp-packaging.yml
on: schedule
log-inputs
4s
Matrix: build_desktop
Matrix: build_tools
build-and-package-ios-tvos
22m 5s
build-and-package-android
13m 35s
Matrix: package_desktop
create-windows-only-package
17m 9s
cleanup-packaging-artifacts
2s
attempt-retry
0s
Annotations
11 errors and 37 warnings
| package-darwin Failed to load artifacts. |
| 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-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. |
| log-inputs Expanded test matrix enabled. |
| 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 2nd, 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 2nd, 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 2nd, 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 2nd, 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 2nd, 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 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/ |
| 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 2nd, 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 2nd, 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 2nd, 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 2nd, 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 2nd, 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 2nd, 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 2nd, 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 2nd, 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 2nd, 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 2nd, 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 2nd, 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 2nd, 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 2nd, 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 2nd, 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 2nd, 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 2nd, 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 2nd, 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 2nd, 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 2nd, 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 2nd, 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 2nd, 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 2nd, 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 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/ |
| final-merge-packages SHA256 (firebase_cpp_sdk.zip) = 2e0ce3709abc617b0b21d8e2ffcfbcfb702b3098034529e1865d3ebe731f1bec |
| 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 2nd, 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 2nd, 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) = dc37a3af5823d7e46309b70c0690539e28c16dfe314fa70ac475e64cb3f46c4a |
| 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 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/ |
| trigger_integration_tests Started workflow integration_tests.yml: https://github.com/firebase/firebase-cpp-sdk/actions/runs/23541307531 |
| trigger_integration_tests Started workflow integration_tests.yml: https://github.com/firebase/firebase-cpp-sdk/actions/runs/23541299365 |
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
| firebase-cpp-sdk-android-package | 70.7 MB | sha256:39024b2c23de631a15e4a3715a558e1df9274ec96ad3375555f34e59d19115a8 | |
| firebase-cpp-sdk-darwin-arm64-Release-static-legacy-build | 364 MB | sha256:163f436bbb31236c8ecf426912a7703060ce6f5d2bc2b60af0f7b24a58da8a25 | |
| firebase-cpp-sdk-darwin-package | 130 MB | sha256:8996b6b5885990eb5e78c764f95f2450af0f56927192b1f329700b9ffc3765e0 | |
| firebase-cpp-sdk-darwin-x64-Release-static-legacy-build | 365 MB | sha256:93cfc9e8a804f726499617d8f6e126d827b4468a91893f6eb72f1642b4d97511 | |
| firebase-cpp-sdk-ios-tvos-package | 107 MB | sha256:9207ed10c89e7e1a7c179828a9c821be47de6b0ad41a0a59d2562fef007183d8 | |
| firebase-cpp-sdk-linux-package | 86.7 MB | sha256:2cfada1d8f5100618dbcbdb94cf3a424b996d1028b68ab4f89d7a17b039848ef | |
| firebase-cpp-sdk-linux-x64-Release-static-c++11-build | 376 MB | sha256:eeef55a25fd584e40f3fca58cf368a7c0fbfcf923414dec591507fc21be9d47b | |
| firebase-cpp-sdk-linux-x64-Release-static-legacy-build | 375 MB | sha256:2cf1c1ce0b5022f41a713f4b80de0558184f2661a94581ce27256d4d03e32a3a | |
| firebase-cpp-sdk-linux-x86-Release-static-c++11-build | 378 MB | sha256:3721f2256df01044bfeea447460cc93b81d868c2c24ab961d79dfb80f1714d5d | |
| firebase-cpp-sdk-linux-x86-Release-static-legacy-build | 376 MB | sha256:6b9a8737231cbe3385d5ebb5cce9edf418b352d529f78d5fb3de154063598f3a | |
| firebase-cpp-sdk-windows-x64-Debug-dynamic-legacy-build | 630 MB | sha256:25a24cc92dbe7a75583d6797bc5c4d5170e2234ee1e026d9be05508e01a40e33 | |
| firebase-cpp-sdk-windows-x64-Debug-dynamic-package | 194 MB | sha256:d49b79d27300537681f8503684c6df34b97bbd22b1ef8e788867cdd1c9759c07 | |
| firebase-cpp-sdk-windows-x64-Debug-static-legacy-build | 660 MB | sha256:39cda23f56804e39fac9a55db26340ed9147af983a71553a287c312b740bf845 | |
| firebase-cpp-sdk-windows-x64-Debug-static-package | 218 MB | sha256:47ff08c4c3ffcdc515ef8fd7bd43477ed35ccc0574dae5d8d1756fda0fb94092 | |
| firebase-cpp-sdk-windows-x64-Release-dynamic-legacy-build | 354 MB | sha256:9a430a41f75f700ef375a26a420755d99d0856c4e13c0d1311a8af1e4da373e3 | |
| firebase-cpp-sdk-windows-x64-Release-dynamic-package | 32 MB | sha256:0ca489c037b96fcb39dda70b6d460da4458d936b011640b2209d3dd44d505e12 | |
| firebase-cpp-sdk-windows-x64-Release-static-legacy-build | 362 MB | sha256:530127e8d5f12b94cf0819e008219028637729484d89275e65dbb740cc057314 | |
| firebase-cpp-sdk-windows-x64-Release-static-package | 39.1 MB | sha256:8cd5a496c9cbe6532a17d80cf9e6b43e24699c0b4eedec2c769faf6e001d793f | |
| firebase-cpp-sdk-windows-x86-Debug-dynamic-legacy-build | 592 MB | sha256:7eb3f40590013f96bec3f31f501644c550befdca7dbe6149615c8c40bc18ab01 | |
| firebase-cpp-sdk-windows-x86-Debug-dynamic-package | 177 MB | sha256:9c68546632a40cc9ab3723cb24aeff88e6dff3bd8a5e201a3f09b286e88e9c6d | |
| firebase-cpp-sdk-windows-x86-Debug-static-legacy-build | 611 MB | sha256:b3c4da6dca5f69a362a77e946bb5075dec00e3884210a697e8aa0fe11e909b87 | |
| firebase-cpp-sdk-windows-x86-Debug-static-package | 197 MB | sha256:a11459a4be464f1a47e280668145b929d476df469d9db6edd321614663aec028 | |
| firebase-cpp-sdk-windows-x86-Release-dynamic-legacy-build | 342 MB | sha256:c60c28285e7fc9f54f0fe45325fab8c4ace99310ef9d695a1218d1da77741d7b | |
| firebase-cpp-sdk-windows-x86-Release-dynamic-package | 25.7 MB | sha256:4226b15bb0e243d65d30537a6ea0bdde7b6198bb97e5a7de17734450cc0dd1bf | |
| firebase-cpp-sdk-windows-x86-Release-static-legacy-build | 348 MB | sha256:2253649af54860ef692414fb9603831b5e1a583bc7a5ab12b4aa3fc146ee6ce7 | |
| firebase-cpp-sdk-windows-x86-Release-static-package | 31 MB | sha256:3c952fc119e7647528515d9465813c9f559776ac39648d3fc1f388b3c227e828 | |
| firebase_cpp_sdk.zip | 1.26 GB | sha256:828e3b0e82d888a0566fb4e88152622bfc836132f94880a366daadc1704ca175 | |
| firebase_cpp_sdk_hash.txt | 256 Bytes | sha256:637c30bba0d00e45479ab6fb2eedffb2520be8a3d902820bbdaf0983f33126a4 | |
| firebase_cpp_sdk_windows.zip | 900 MB | sha256:de529c5c161b2938f13945cd6a8cd46c3d8d7d23ba2ab696fb70b1336d289a69 | |
| firebase_cpp_sdk_windows_hash.txt | 280 Bytes | sha256:295b00c7abb4cec22a0e90a8b44ef8545439397b3dd3bee58ed047be73865998 | |
| packaging-tools-darwin | 46.1 MB | sha256:f512d849da03b64d0f371ff01adcf1984f1836b9008191d071db3af53ad73ee6 | |
| packaging-tools-linux | 268 MB | sha256:e1d671bf6409a0de1e81688387ffad1cd1cad7bfdd3bf741cb4c8235f4168356 | |