Compatibility¶
The repository establishes the following compatibility baseline:
| Component | Repository-backed status for 4.0.x |
|---|---|
| Java | Compiled with --release 17; the full test suite runs on JDK 17, 21, and 25 |
| Logback Classic | Built and tested with 1.6.3; dependency scope is provided |
| Logback Access | Compiled against ch.qos.logback.access:logback-access-common:2.0.15; dependency scope is provided |
| SLF4J | Compiled against 2.0.18; dependency scope is provided |
| Jackson | Built and tested with Jackson 3.2.2 (tools.jackson) |
| Logstash Logback Encoder | Built and tested with 9.0 |
| AWS SDK | Built and tested with the AWS SDK for Java 2.54.4; required modules have provided scope |
| Elasticsearch | End-to-end Bulk API integration tests run against Elasticsearch 8.19.20 and 9.5.1 with security disabled |
| OpenSearch | End-to-end Bulk API integration tests run against OpenSearch 2.19.6 and 3.7.0 without the Security plugin |
Java compatibility¶
| Appender version | Minimum Java version | CI-tested JDKs |
|---|---|---|
4.0.0 |
Java 17 (--release 17) |
17, 21, 25 |
3.1.3 |
Java 11 (--release 11) |
11, 21, 25 |
3.1.2 |
Java 11 (--release 11) |
11, 21, 25 |
Java 17 is the bytecode baseline for version 4.0.0. JDK 17, 21, and 25 are explicitly verified by the complete CI test suite; intermediate and newer JDK releases are expected to work but are not separately verified. Applications that must remain on Java 11 should stay on the 3.1.x line.
Warning Version 3.1.x is the final release line supporting Java 11 and is no longer actively maintained. Upstream fixes are not available for the affected dependency versions. Replacing them with newer major versions within the 3.1.x line would risk substantial binary, runtime, and behavioral incompatibilities.
The remaining dependency findings therefore cannot be safely remediated in-place. Users should migrate to version 4.x and Java 17 or newer. No further dependency updates or security backports are planned for 3.1.x.
Newer Logback, SLF4J, Elasticsearch, or OpenSearch combinations may work, but they are not guaranteed by the current build and test configuration. If you depend on a specific combination, run the test suite and an integration test against that stack before deploying.