deps: bump livekit/protocol for golang-jwt/xsync v4/stdlib errors#29
Merged
Conversation
boks1971
approved these changes
Jun 4, 2026
Only direct dep change: livekit/protocol bumped to a7a83da5 (the upstream go-get-u sweep). Transitive updates pulled in via tidy. No newer-major direct dep candidates. +incompatible: aliyun-oss-go-sdk v3.0.2+incompatible (transitive, upstream choice).
Pin protocol to a7a83da5 and run go get -u ./... sweep.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
go get -usweep —go.mod/go.sumonly, no source changes.livekit/protocol:go-jose/v3→golang-jwt/jwt/v5(avoids go-jose v4 HS256 ≥32-byte minimum that breaks short OSS dev secrets)puzpuzpuz/xsync/v3→/v4pkg/errors→ stdliberrors+fmt.Errorf %wCoordinated upstream: livekit/protocol#1606, livekit/cloud-protocol#1222, livekit/backend-common#891.
Test plan
go build ./...go test ./...(pre-existing failures requiring Docker / Postgres / AWS creds)