You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by ma...@apache.org on 2021/12/14 06:04:30 UTC

[logging-log4j2] branch release-2.x updated: LOG4J2-3222: Fix typo in version

This is an automated email from the ASF dual-hosted git repository.

mattsicker pushed a commit to branch release-2.x
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git


The following commit(s) were added to refs/heads/release-2.x by this push:
     new 3a63d27  LOG4J2-3222: Fix typo in version
3a63d27 is described below

commit 3a63d2702416fbc2793e40093a586d949a0f0fae
Author: Matt Sicker <bo...@gmail.com>
AuthorDate: Tue Dec 14 00:04:02 2021 -0600

    LOG4J2-3222: Fix typo in version
---
 src/site/markdown/index.md.vm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/site/markdown/index.md.vm b/src/site/markdown/index.md.vm
index 3ca59de..1267cbe 100644
--- a/src/site/markdown/index.md.vm
+++ b/src/site/markdown/index.md.vm
@@ -137,8 +137,8 @@ dependencies.
 
 $h2 News
 
-Log4j 2.15.1 has been released solely to disable access to JNDI by default. The CVE noted below was fixed in the 2.15.0
-release. 2.15.1 is NOT a required upgrade but users may choose to use it to have confidence that JNDI will not be
+Log4j 2.16.0 has been released solely to disable access to JNDI by default. The CVE noted below was fixed in the 2.15.0
+release. 2.16.0 is NOT a required upgrade but users may choose to use it to have confidence that JNDI will not be
 abused.
 
 $h3 CVE-2021-44228