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

andor pushed a commit to branch branch-3.9
in repository https://gitbox.apache.org/repos/asf/zookeeper.git


The following commit(s) were added to refs/heads/branch-3.9 by this push:
     new 8f88dcd45 Note breaking change for slf4j-api and logback-classic 
upgrade
8f88dcd45 is described below

commit 8f88dcd45cbc0c80748b73a951f45cebeac173c4
Author: Kezhu Wang <kez...@apache.org>
AuthorDate: Wed Aug 20 03:16:28 2025 +0800

    Note breaking change for slf4j-api and logback-classic upgrade
    
    Reviewers: anmolnar
    Author: kezhuw
    Closes #2298 from kezhuw/note-breaking-change-for-slf4j-logback-upgrade-3.9
---
 zookeeper-docs/src/main/resources/markdown/releasenotes.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/zookeeper-docs/src/main/resources/markdown/releasenotes.md 
b/zookeeper-docs/src/main/resources/markdown/releasenotes.md
index 4ad940550..33c58ffd4 100644
--- a/zookeeper-docs/src/main/resources/markdown/releasenotes.md
+++ b/zookeeper-docs/src/main/resources/markdown/releasenotes.md
@@ -16,6 +16,18 @@ limitations under the License.
 
 
 # Release Notes - ZooKeeper - Version 3.9.4
+
+## Breaking changes
+[ZOOKEEPER-4891](https://issues.apache.org/jira/browse/ZOOKEEPER-4891) updates 
`logback-classic` to `1.3.15` to solve cve issues and
+`slf4j-api` to `2.0.13` to meet compatibilty requirement of logback.
+
+This could cause slf4j to complain "No SLF4J providers were found" and output 
no further logs in certain conditions.
+1. For library or client usage, this could happen if you specify and inherit 
incompatible slf4j and logback versions, say, `slf4j-api:2.0.13` from
+   `org.apache.zookeeper:zookeeper` and `logback-classic:1.2.13` from 
customized project dependencies.
+2. For application or deployment usage, this could happen if you custom and 
inherit incompatible slf4j and logback versions in classpath, say,
+   `slf4j-api:2.0.13` from zookeeper distribution and `logback-classic:1.2.13` 
from customization.
+
+This could be solved by specifying compatiable slf4j and logback versions in 
classpath, say, `slf4j-api:2.0.13` and `logback-classic:1.3.15`.
                 
 ## Bug
 

Reply via email to