Fix Bookworm protobuf package pins - #899
Merged
Merged
Conversation
tconley1428
marked this pull request as ready for review
September 9, 2026 23:19
Sushisource
approved these changes
Sep 9, 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
2 participants
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
Update the Python and TypeScript image Dockerfiles to install the protobuf packages available in Debian Bookworm (
3.21.12*).The Bookworm base-image migration retained the prior Bullseye-only
3.12.4*pins, causing Docker builds to fail duringapt-get install.Validation
main(for example, CI run 34252304325), so this is independent of the System Nexus PR.git diff --checkpasses.