Skip to content

Unified CI workflow for smarter PR gating (#148) #34

Unified CI workflow for smarter PR gating (#148)

Unified CI workflow for smarter PR gating (#148) #34

Triggered via push June 3, 2026 23:45
Status Success
Total duration 34m 37s
Artifacts 12

ci.yml

on: push
Detect Changes
7s
Detect Changes
License Check  /  License Check
7s
License Check / License Check
Matrix: Builds / build
Matrix: Tests / test
Builds  /  Build (docker-linux-arm64)
0s
Builds / Build (docker-linux-arm64)
Builds  /  Build (docker-linux-x64)
0s
Builds / Build (docker-linux-x64)
Tests  /  Code Coverage
15m 44s
Tests / Code Coverage
C++ Checks  /  clang-format
27s
C++ Checks / clang-format
C++ Checks  /  clang-tidy
10m 42s
C++ Checks / clang-tidy
Generate Docs  /  Generate and verify docs
31s
Generate Docs / Generate and verify docs
Builds  /  Build (cpp-example-collection-linux-arm64)
0s
Builds / Build (cpp-example-collection-linux-arm64)
Builds  /  Build (cpp-example-collection-x64)
0s
Builds / Build (cpp-example-collection-x64)
Fit to window
Zoom out
Zoom in

Annotations

11 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.
Tests / Test (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.
Tests / Test (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.
Tests / Code Coverage
(WARNING) /home/runner/work/client-sdk-cpp/client-sdk-cpp/src/logging.cpp:53: Ignoring negative hits in: branch 7 taken -10.
Tests / Code Coverage
(WARNING) /home/runner/work/client-sdk-cpp/client-sdk-cpp/src/logging.cpp:33: Ignoring negative hits in: branch 7 taken -24.
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.
Tests / Test (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.
Tests / Test (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.
Tests / Test (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 (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/
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
coverage-report
516 KB
sha256:96f9dbb44575f4690f9b77917c04dccdeb2de43d4a90a1b7c5f7085938e79ae9
livekit-cpp-docs
2.54 MB
sha256:aa5501329196de23c87949b7c9343479b7f6f2ca445d53e90f0aaceb4284d795
livekit-sdk-linux-arm64
23.1 MB
sha256:0c1c22f41fd233c4726591dfc830a457cbfca30f86c863fdd3d0c223fe63da9d
livekit-sdk-linux-x64
24.7 MB
sha256:d9539b7cac77f8e277851e7f7e65e1d79a7f769dd45e04da85102778a0a17478
livekit-sdk-macos-arm64
18.9 MB
sha256:244855f353a7e079cc2488ad43e66ca224ade4d588c4f51abb3988d467c396cd
livekit-sdk-macos-x64
19.8 MB
sha256:f522da74c0470e4b306cbbc90ef0d1f12cedbe57b9e195e3ea805df56608bb3b
livekit-sdk-windows-x64
11.3 MB
sha256:791349f1232eed205687ca7acc4cb34c2fc22af5aadaf3932800f6faf1c544cb
test-results-linux-arm64
1.45 MB
sha256:470e735ad22bda8d01f100be76bcff02d950a1e690440589a810ed29bf36a6ff
test-results-linux-x64
1.46 MB
sha256:3ae237b0c4d375835c4f209ebd33247b46029cb6f33c71dd67b2b0f68ca9a5a3
test-results-macos-arm64
1.35 MB
sha256:7b76d04ab2b759446c9150a562a8c7c8b32e038e9a240813e67e0564acef92f6
test-results-macos-x64
1.56 MB
sha256:192f11ba6a5174dd383ad6146ef268b3db9eac2660653a6ac888823d831c248b
test-results-windows-x64
6 KB
sha256:9a01240b6fa48edb555c8dba768f0b2492235a15e60e304a140f4f595e056b2b