Update infrastructure dependencies for v2026.2 - #2022
Merged
Conversation
Newer versions have been released but less than 14 days ago. None of the high priority CVEs fixed affect us.
It was released only a week ago but it fixes additional buffer overread and overflow issues over 1.31.1 released a month ago.
2.0.0 was released 3 weeks ago and followed up with point releases. Let's wait until it stabilizes, we don't need any of the udpates.
8.8 has been out a month but it makes some significant changes so I'd rather be conservative
lognaturel
changed the title
sadiqkhoja
approved these changes
Jun 29, 2026
9 tasks
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.
Closes #1805
What has been done to verify that this works as intended?
Ran branch on dev, verified basic functionality. I only tried email relaying. Since we stayed in the 1.2.x line I think that's enough.
Why is this the best possible solution? Were any other approaches considered?
See each commit for an explanation of the versions I picked. I generally followed our 2 week cooldown policy except for the nginx point release.
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
This is pretty conservative so it should fix vulnerabilities with low risk. I think the smtp version bump is always the riskiest because we don't have a great way to verify local email. Very few providers allow that now anyway.
Does this change require updates to documentation? If so, please file an issue here and include the link below.
No
Before submitting this PR, please make sure you have:
nextbranch OR only changed documentation/infrastructure (masteris stable and used in production)