.github/workflows/cpp-packaging.yml #3832
a-mauricecpp-packaging.yml
on: schedule
log-inputs
2s
Matrix: build_desktop
Matrix: build_tools
build-and-package-ios-tvos
18m 1s
build-and-package-android
13m 32s
Matrix: package_desktop
create-windows-only-package
15m 59s
cleanup-packaging-artifacts
3s
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-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.
|
|
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-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-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-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-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-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. 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-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-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-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-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-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-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-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-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-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-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-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. 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) = 5045d18bd7f3763e17ad1adf96bb7e93f2ee27e3ec6052ed53e2ae15e530b497
|
|
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) = e5980080395fde6aeaa898b10195ef6b57c58550126534edbdbb085175cd6d01
|
|
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. 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/23342842730
|
|
trigger_integration_tests
Started workflow integration_tests.yml: https://github.com/firebase/firebase-cpp-sdk/actions/runs/23342835889
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
firebase-cpp-sdk-android-package
Expired
|
70.7 MB |
sha256:188233a88cf0944525648db7a57291c948cdb28e9f9ba2634d54e81b788fb031
|
|
|
firebase-cpp-sdk-darwin-arm64-Release-static-legacy-build
Expired
|
364 MB |
sha256:da4fea6a5de2458f8701f183a2c05947f89e314cb6c906cec9c42322be642f23
|
|
|
firebase-cpp-sdk-darwin-package
Expired
|
130 MB |
sha256:b0eec62a06a1f6d8bba6dea88969fbc217be8e6a975ca2b442e74247e9a0fd01
|
|
|
firebase-cpp-sdk-darwin-x64-Release-static-legacy-build
Expired
|
364 MB |
sha256:c2c8635d700c5d37eb05a297823b595f40280a4d9bf11cfccc1de5680875d731
|
|
|
firebase-cpp-sdk-ios-tvos-package
Expired
|
107 MB |
sha256:63e3945ea4e98d7135b90549f02a7431da8d1374fb8c8eeb95fab4ca9ec1edd7
|
|
|
firebase-cpp-sdk-linux-package
Expired
|
86.7 MB |
sha256:be5568d652761dec21d96e49e442ba3d4c6fc21c3ff00156807e042ff6f375ae
|
|
|
firebase-cpp-sdk-linux-x64-Release-static-c++11-build
Expired
|
376 MB |
sha256:d6b8a3f62bf058aeb44577e4213fdaaf3cb01bb05dac70b872776e4cdb37343a
|
|
|
firebase-cpp-sdk-linux-x64-Release-static-legacy-build
Expired
|
375 MB |
sha256:ccf7e0c1a180249e1dac937b377835c8a71a4499257e37cef7d49bddda53c772
|
|
|
firebase-cpp-sdk-linux-x86-Release-static-c++11-build
Expired
|
377 MB |
sha256:7603080f04a9f993ac14caa9ee1371349f4edf4bb6deabdfa07c438469ef10d3
|
|
|
firebase-cpp-sdk-linux-x86-Release-static-legacy-build
Expired
|
376 MB |
sha256:8333687cc48f52426582e66ac1ef7460826c5deee7693f98cce7ba8776bf700a
|
|
|
firebase-cpp-sdk-windows-x64-Debug-dynamic-legacy-build
Expired
|
630 MB |
sha256:3010c8f3d66f49ededf3bcb83257638de41d8d861431ccc518cf5adfad18dc5f
|
|
|
firebase-cpp-sdk-windows-x64-Debug-dynamic-package
Expired
|
194 MB |
sha256:6fad38ce9b1961319ecc9739164e03fa3ef4b1329b44c3915d64282472d46db0
|
|
|
firebase-cpp-sdk-windows-x64-Debug-static-legacy-build
Expired
|
660 MB |
sha256:1c71e33a1dcb970ef85bbfce2dbc04f0caffd5fb89ceac118e4d8c3e897667b1
|
|
|
firebase-cpp-sdk-windows-x64-Debug-static-package
Expired
|
218 MB |
sha256:eaaa67df502cd1459a85cd8d0ecad15774b5c91b1dd676a5631c3301fbbdfff6
|
|
|
firebase-cpp-sdk-windows-x64-Release-dynamic-legacy-build
Expired
|
354 MB |
sha256:f295fedb4c2348058f151f54fac0031024817112b5502ddaf34f124ea8005ae1
|
|
|
firebase-cpp-sdk-windows-x64-Release-dynamic-package
Expired
|
32 MB |
sha256:23a8dee259c29119829a8cfaf78ab093680004b0989ce5c6e5ecc72480b4bad5
|
|
|
firebase-cpp-sdk-windows-x64-Release-static-legacy-build
Expired
|
362 MB |
sha256:ca8183dea1df9c489990ebd61e1b260c00abd51ac8bcc149310a127efa425c70
|
|
|
firebase-cpp-sdk-windows-x64-Release-static-package
Expired
|
39.1 MB |
sha256:6af56f6863951b43f4bd4e96315de5b1789ca6f5b19c94b0a2499f24102c7b61
|
|
|
firebase-cpp-sdk-windows-x86-Debug-dynamic-legacy-build
Expired
|
592 MB |
sha256:385e0bd33cc3f8e06969565e2e4054b19d5d85bb8d9cfdd5bedede3237472274
|
|
|
firebase-cpp-sdk-windows-x86-Debug-dynamic-package
Expired
|
177 MB |
sha256:b05e5afc64f4c207d042c6b678f18d0cbac14702b2bb09a91c981d92644b650c
|
|
|
firebase-cpp-sdk-windows-x86-Debug-static-legacy-build
Expired
|
611 MB |
sha256:3a175624fd409d2e71552af7eec93d6f9f05d29051251201cf4b2ebe617f52eb
|
|
|
firebase-cpp-sdk-windows-x86-Debug-static-package
Expired
|
197 MB |
sha256:d7908d0c2b49cbc1441c91c07e415618ac047fc8619ec5534ffc8ee7224ee508
|
|
|
firebase-cpp-sdk-windows-x86-Release-dynamic-legacy-build
Expired
|
342 MB |
sha256:af6bc6c627809e6ede34bdd99aaf26707d401a6661bf2a88bce7bb391abe22c4
|
|
|
firebase-cpp-sdk-windows-x86-Release-dynamic-package
Expired
|
25.7 MB |
sha256:d2b0486337adbe46ce058c7b4378dde3e92402051f88cad9fb65db13e596c041
|
|
|
firebase-cpp-sdk-windows-x86-Release-static-legacy-build
Expired
|
348 MB |
sha256:a693e923d3c1ca57dbeae25efd29e869135028662ad19f3d26c9f8bea605dbc5
|
|
|
firebase-cpp-sdk-windows-x86-Release-static-package
Expired
|
31 MB |
sha256:556d5c989aa49dcd90a1f44282bc0167794c9a3cdc51168a2598dbd72b5539b2
|
|
|
firebase_cpp_sdk.zip
Expired
|
1.26 GB |
sha256:770d8e3eab251dace61998a8d09236dffa85c6470e1e75dedc904019bde895cb
|
|
|
firebase_cpp_sdk_hash.txt
Expired
|
256 Bytes |
sha256:1d4a62aabeb216ec14da0109d356816d7cfeefd4de144aa94947dbfd2adf96d5
|
|
|
firebase_cpp_sdk_windows.zip
Expired
|
900 MB |
sha256:bfaad974d91b9b24b20c47a78e75082b1285c55ed0255693300f2c823eb8c261
|
|
|
firebase_cpp_sdk_windows_hash.txt
Expired
|
280 Bytes |
sha256:3b6c6ef242153845b234a53adfe4050c9a5c7ccaa6379334b569d20d8656d0b4
|
|
|
packaging-tools-darwin
Expired
|
46.1 MB |
sha256:99d67ae499d068c3e182ad18b6a0106eeca5e8500f30f7660561afd4443eabec
|
|
|
packaging-tools-linux
Expired
|
268 MB |
sha256:07c453d773cbc97628593b1e0d1d51e90541ec9ed910157e010d066095548ac8
|
|