feat: security vulnerability patches for version 4#16390
Closed
hbrysiewicz wants to merge 6 commits into
Closed
Conversation
Member
|
I think it's better to publish your own fork of v4 with these changes. We do not have enough knowledge or the ability to run proper testing that we would be comfortable with merging this. And if we would backport this to v4, we should do this for v5 as well. |
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.
Pull Request Checklist
Description Of Change
This backports some critical security fixes that were applied to v6+ into v4. While I know its probably better to upgrade (and we are working towards it), I thought this might also be useful to anyone else still for some insane reason running v4 😬 .
The following are the fixes applied and their relevant PR for v6: