Repository navigation
fix(tests): pin toxiproxy to v2.12.0 - #7676
Merged
Merged
Conversation
Upstream master now requires Go 1.27, which breaks the golang:1.25 builder used by the plugin test docker-compose setup. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
u9g
approved these changes
Oct 8, 2026
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.
tests/Dockerfile.toxiproxyclones Shopify/toxiproxy frommaster. Upstream switched to Go 1.27 today (Shopify/toxiproxy@f83c9865e), but our builder image isgolang:1.25, so the image build fails with:This breaks every
livekit-plugins-*CI job, onmainas well as on PRs. The fix pins the clone to the latest release,v2.12.0, which needs Go 1.23. I built the image locally with this change.🤖 Generated with Claude Code