v2.4.0.2

What's Changed

• Add Ruby 3.2.x support by @abrom in #36

Full Changelog: v2.4.0.1...v2.4.0.2

v1.28.5.1

Update Apache Tika to v1.28.5

Full Changelog: v1.28.4.1...v1.28.5.1

v1.28.4.1

Update Apache Tika to v1.28.4

Full Changelog: v1.28.3.2...v1.28.4.1

v1.28.3.2

What's Changed

• Add Ruby 3.2.x support by @abrom in #37

Full Changelog: v1.28.3.1...v1.28.3.2

v2.4.0.1

What's Changed

• Add Github actions in favour of Travis CI by @abrom in #29
• Version bump to v2.4.0.1 by @abrom in #30

Full Changelog: v2.3.0.1...v2.4.0.1

v1.28.3.1

What's Changed

• Version bump to v1.28.3.1 by @abrom in #34

The most notable changes in Tika 1.28.3 over the previous release are:

Security and general dependency upgrades.

Full Changelog: v1.28.2.1...v1.28.3.1

v1.28.2.1

What's Changed

• Version bump to v1.28.2.1 by @abrom in #33

The most notable changes in Tika 1.28.2 over the previous release are:

Security and general dependency upgrades.

Full Changelog: v1.28.1.1...v1.28.2.1

v1.28.1.1

What's Changed

• Version bump to v1.28.1.1 by @abrom in #32

The most notable changes in Tika 1.28.1 over the previous release are:

Security upgrades: xerces, log4j2, junrar and protobuf (TIKA-3671 and TIKA-3638).
General dependency upgrades (TIKA-3671).

Full Changelog: v1.28.1...v1.28.1.1

v1.28.1

What's Changed

• Version bump to v1.28.1 by @abrom in #31

Update Tika to v1.28
see https://tika.apache.org/1.28/index.html

Upgrade to log4j 2.17.0 (TIKA-3625)
Upgrade PDFBox to 2.0.25 (TIKA-3622)
Upgrade log4j 1.x to log4j2 2.16.0. Users will likely want to upgrade their logging configurations from log4jto log4j2 (TIKA-3618).

Full Changelog: v1.27.1...v1.28.1

v2.3.0.1

What's Changed

• Version bump to v2.3.0.1 by @abrom in #27

Updates Tika to v2.3.0

This includes:

• an upgrade of log4j2 to v2.17.1
• non-trivial upgrade of Apache POI which will result in significantly more logging output.

The additional POI log output appears to be in the form of an error dump related to:

org.apache.poi.util.XMLHelper SAX Feature unsupported

I haven't been able to find a solution for this, however the log4j upgrade may outweigh the additional logging?

Full Changelog: v2.2.1.2...v2.3.0.1