Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Upgrade Log4j to 2.16.0 #6979

Merged
merged 1 commit into from
Dec 14, 2021
Merged

chore: Upgrade Log4j to 2.16.0 #6979

merged 1 commit into from
Dec 14, 2021

Conversation

kingthorin
Copy link
Member

Updated build file and LOGALNOTICE.

Signed-off-by: kingthorin kingthorin@users.noreply.github.com

Updated build file and LOGALNOTICE.

Signed-off-by: kingthorin <kingthorin@users.noreply.github.com>
@thc202 thc202 merged commit 7096123 into zaproxy:main Dec 14, 2021
@kingthorin kingthorin deleted the log4j-216 branch December 14, 2021 22:47
@thc202
Copy link
Member

thc202 commented Dec 14, 2021

Thank you!

@samuelgozi
Copy link

When will this be included in a release?

@thc202
Copy link
Member

thc202 commented Dec 15, 2021

There's no planned main release, this does not affect ZAP. It will be included in the weekly release next week (usually) though.

@github-actions
Copy link

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Mar 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

Successfully merging this pull request may close these issues.

None yet

4 participants