docs: weekly go-livepeer changelog (May 13, 2026)#897
Merged
Conversation
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
📊 V2 Browser Sweep Results❌ Test report not found. The test may have failed before report generation.
|
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
Adds this week's go-livepeer changelog entry covering changes merged since the last update.
Changes
GET /{channel}/nextendpoint (trickle: Add a /<channel>/next endpoint go-livepeer#3925).lastVerifiedto2026-05-13.Context
Only one user-facing PR merged to
livepeer/go-livepeerbetween 2026-05-07 and 2026-05-13: a new trickle/nextroute that lets publishers/SDKs probe the server for the next sequence number before their first POST, fixing a fresh-channel race that could drop the first segment.