Skip to content

Update module github.com/livekit/server-sdk-go/v2 to v2.16.3 - autoclosed #3152

Update module github.com/livekit/server-sdk-go/v2 to v2.16.3 - autoclosed

Update module github.com/livekit/server-sdk-go/v2 to v2.16.3 - autoclosed #3152

Triggered via pull request May 12, 2026 20:39
Status Failure
Total duration 5m 57s
Artifacts

build.yaml

on: pull_request
Build (no console, no CGO)
1m 46s
Build (no console, no CGO)
lint-and-test
2m 8s
lint-and-test
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

26 errors and 6 warnings
Build (no console, no CGO)
Process completed with exit code 1.
Build (no console, no CGO): cmd/lk/agent.go#L1025
not enough arguments in call to agentsClient.StreamLogs
Build (no console, no CGO): cmd/lk/agent.go#L675
not enough arguments in call to agentsClient.StreamLogs
lint-and-test
Process completed with exit code 1.
lint-and-test: cmd/lk/agent.go#L1025
not enough arguments in call to agentsClient.StreamLogs
lint-and-test: cmd/lk/agent.go#L675
not enough arguments in call to agentsClient.StreamLogs
lint-and-test: cmd/lk/agent.go#L1025
not enough arguments in call to agentsClient.StreamLogs
lint-and-test: cmd/lk/agent.go#L675
not enough arguments in call to agentsClient.StreamLogs
build (macos-latest, darwin_arm64)
Process completed with exit code 1.
build (macos-latest, darwin_arm64): cmd/lk/agent.go#L1025
not enough arguments in call to agentsClient.StreamLogs
build (macos-latest, darwin_arm64): cmd/lk/agent.go#L675
not enough arguments in call to agentsClient.StreamLogs
build (ubuntu-latest, windows_arm64, aarch64-windows-gnu, windows, arm64)
Process completed with exit code 1.
build (ubuntu-latest, windows_arm64, aarch64-windows-gnu, windows, arm64): cmd/lk/agent.go#L1025
not enough arguments in call to agentsClient.StreamLogs
build (ubuntu-latest, windows_arm64, aarch64-windows-gnu, windows, arm64): cmd/lk/agent.go#L675
not enough arguments in call to agentsClient.StreamLogs
build (ubuntu-latest, linux_amd64, x86_64-linux-gnu.2.28, amd64, x86_64-linux-gnu)
Process completed with exit code 1.
build (ubuntu-latest, linux_amd64, x86_64-linux-gnu.2.28, amd64, x86_64-linux-gnu): cmd/lk/agent.go#L1025
not enough arguments in call to agentsClient.StreamLogs
build (ubuntu-latest, linux_amd64, x86_64-linux-gnu.2.28, amd64, x86_64-linux-gnu): cmd/lk/agent.go#L675
not enough arguments in call to agentsClient.StreamLogs
build (ubuntu-latest, windows_amd64, x86_64-windows-gnu, windows, amd64)
Process completed with exit code 1.
build (ubuntu-latest, windows_amd64, x86_64-windows-gnu, windows, amd64): cmd/lk/agent.go#L1025
not enough arguments in call to agentsClient.StreamLogs
build (ubuntu-latest, windows_amd64, x86_64-windows-gnu, windows, amd64): cmd/lk/agent.go#L675
not enough arguments in call to agentsClient.StreamLogs
lint-and-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
build (ubuntu-latest, windows_arm64, aarch64-windows-gnu, windows, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mlugg/setup-zig@d1434d08867e3ee9daa34448df10607b98908d29. 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 (ubuntu-latest, linux_amd64, x86_64-linux-gnu.2.28, amd64, x86_64-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mlugg/setup-zig@d1434d08867e3ee9daa34448df10607b98908d29. 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 (ubuntu-latest, windows_amd64, x86_64-windows-gnu, windows, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mlugg/setup-zig@d1434d08867e3ee9daa34448df10607b98908d29. 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 (ubuntu-latest, linux_arm, arm-linux-gnueabihf.2.28, armhf, arm-linux-gnueabihf, arm, 7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mlugg/setup-zig@d1434d08867e3ee9daa34448df10607b98908d29. 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 (ubuntu-latest, linux_arm64, aarch64-linux-gnu.2.28, arm64, aarch64-linux-gnu, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mlugg/setup-zig@d1434d08867e3ee9daa34448df10607b98908d29. 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/