chore: use :broadway v1.3 over forked copy#3680
Open
amokan wants to merge 1 commit into
Open
Conversation
djwhitt
approved these changes
Jul 11, 2026
djwhitt
left a comment
Contributor
There was a problem hiding this comment.
Reviewed the changelog. Looks low risk, and I really want that process labeling capability.
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.
This is one we'll want to monitor on staging/canary, but this seems like a solid and low-risk move.
We've been using our own fork of Broadway for some time, but I noticed that the pinned branch we were on is actually in the canonical Broadway repo and is included in the latest v1.3 release.
Delta between our forked/pinned branch and Broadway v1.3 can be found here - Logflare/broadway@fix/batcher-fullsweep-after...elixir-broadway:broadway:v1.3.0
Here is Ziinc's merged PR into Broadway from the pinned version we were on.
Why Switch To v1.3?
A couple standout items that could be beneficial to us in one way or another are: