Skip to content

Additional CI improvments #42

Additional CI improvments

Additional CI improvments #42

Triggered via pull request June 4, 2026 01:29
Status Success
Total duration 31m 21s
Artifacts 8

ci.yml

on: pull_request
Detect Changes
4s
Detect Changes
License Check  /  License Check
6s
License Check / License Check
Matrix: Builds / build
Matrix: Tests / test
Waiting for pending jobs
Builds  /  Build (docker-linux-arm64)
22m 26s
Builds / Build (docker-linux-arm64)
Builds  /  Build (docker-linux-x64)
25m 37s
Builds / Build (docker-linux-x64)
Generate Docs  /  Generate and verify docs
35s
Generate Docs / Generate and verify docs
C++ Checks  /  clang-format
C++ Checks / clang-format
C++ Checks  /  clang-tidy
C++ Checks / clang-tidy
Tests  /  Code Coverage
Tests / Code Coverage
Builds  /  Build (cpp-example-collection-linux-arm64)
5m 0s
Builds / Build (cpp-example-collection-linux-arm64)
Builds  /  Build (cpp-example-collection-x64)
5m 26s
Builds / Build (cpp-example-collection-x64)
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
Builds / Build (macos-arm64)
The following taps are not trusted: aws/tap azure/bicep hashicorp/tap Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep brew trust --formula hashicorp/tap/packer You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep hashicorp/tap Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep hashicorp/tap To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
Builds / Build (windows-x64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: lukka/run-vcpkg@6fe69898af670ac05f4a8427cc5cff4fb361cee5. 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/
Builds / Build (macos-x64)
The following taps are not trusted: aws/tap azure/bicep hashicorp/tap Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep brew trust --formula hashicorp/tap/packer You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep hashicorp/tap Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep hashicorp/tap To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
Builds / Build (docker-linux-arm64)
The command [sudo apt-get remove -y azure-cli google-chrome-stable firefox powershell mono-devel libgl1-mesa-dri --fix-missing] failed to complete successfully. Proceeding...
Builds / Build (cpp-example-collection-linux-arm64)
The command [sudo apt-get remove -y azure-cli google-chrome-stable firefox powershell mono-devel libgl1-mesa-dri --fix-missing] failed to complete successfully. Proceeding...
CI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: suzuki-shunsuke/required-status-check-action@2b5a46064846b09381852c2c4217e898f639e768. 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/

Artifacts

Produced during runtime
Name Size Digest
livekit-cpp-docs
2.54 MB
sha256:7cb1224f14538daee127736b719342cd5318fcdb80b54465e60d656038d10876
livekit-cpp-sdk-docker-arm64
1.71 GB
sha256:fdf11a03ce0d959ea9c0e6de974bc96ac49b0fdc9d3434a755831f7711de7829
livekit-cpp-sdk-docker-x64
1.8 GB
sha256:a2681b4ddf4740202ce19f381efcb65bc53973175801c47ae6fb8f27547810c9
livekit-sdk-linux-arm64
23.1 MB
sha256:ca82b42d3c7cf6cb8a30778c0c6be24f70cbca998136f8bcb118ed770b530940
livekit-sdk-linux-x64
24.7 MB
sha256:97ba55aa4ade8c49465c20d4dcbe9e93e2974aa49ed9675dd31d0f3f4dd17e94
livekit-sdk-macos-arm64
18.9 MB
sha256:e1bf662a02996915142cca61ff2277961addc96f451536d9444f2a73d5ccf5c0
livekit-sdk-macos-x64
19.8 MB
sha256:c4dda784e3c7ccc82589e26f48bcefec438f08897dba7201580e17a39c21aa81
livekit-sdk-windows-x64
11.3 MB
sha256:894ed00c69a66a04ffde65c4aad4a25086851a3dc393d6260690b68e36f091a2