renovate: bump the protocol submodule automatically - #793
Open
u9g wants to merge 1 commit into
Open
Conversation
u9g
requested review from
cloudwebrtc,
lukasIO and
xianshijing-lk
as code owners
August 25, 2026 21:26
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
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
1 participant
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.
Every bump of
livekit-protocol/protocolso far has been a hand-made PR (#786, #780, #775), so a merged proto change sits unpublished until someone remembers to do it. Renovate'sgit-submodulesmanager is off by default; this turns it on so each new commit on protocolmainshows up as a PR here. The existingbuild-protocolworkflow already regenerates the_pb2stubs onto any PR that toucheslivekit-protocol/, so those PRs come out complete.Scoped to the protocol submodule:
livekit-rtc/rust-sdksis opted out, since bumping it means an FFI rebuild and is a separate decision.minimumReleaseAgedoes not hold these back — the git-refs datasource carries no release timestamp, so the check has nothing to evaluate against.