update h11 via httpx#856
Merged
Merged
Conversation
agnesgaroux
approved these changes
Jun 9, 2025
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.
What does this change?
This updates h11 to a version that does not suffer from CVE-2025-43859
Resolving
See also: wellcomecollection/catalogue-pipeline#2920
Part of wellcomecollection/platform#5796
How to test
Everything should just work exactly the same as before
How can we measure success?
Three fewer vulnerability warnings reported by Dependabot
Have we considered potential risks?
We do not directly use h11, so it is unlikely that this will cause any issues - if the developers of httpcore and httpx are happy with it, then so are we.
If things stop working, then we can roll this back.