Hikit icon indicating copy to clipboard operation
Hikit copied to clipboard

Published 20 hours ago • verified publisher icon SeC-Hikit

Bump org.apache.tika:tika-core from 1.25 to 1.28.3 in /backend

Open dependabot[bot] opened this issue 3 months ago • 1 comments

Bumps org.apache.tika:tika-core from 1.25 to 1.28.3.

Changelog

Sourced from org.apache.tika:tika-core's changelog.

Release 1.28.3 - 5/23/2022

  • General dependency upgrades (TIKA-3770).

Release 1.28.2 - 4/26/2022

  • General dependency upgrades (TIKA-3688).

  • Upgrade to PDFBox 2.0.26 (TIKA-3726).

  • Upgrade to Apache POI 5.2.0. This is the first upgrade to POI 5.x and represents a major refactoring. Users will experience significantly more logging (TIKA-3678).

Release 1.28.1 - 2/8/2022

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

  • General dependency upgrades (TIKA-3671).

Release 1.28 - 12/19/2021

  • Upgrade log4j to 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 log4j to log4j2 (TIKA-3618).

  • General dependency upgrades (TIKA-3613).

Release 1.27 - 06/30/2021

  • Migrate MP4 parsing to Drew Noakes' metadata-extractor (TIKA-3459). To revert to legacy parser turn off NoakesMP4Parser and turn on MP4Parser via tika-config.xml.

  • Prevent rare infinite loop in tika-server's -spawnChild mode when restart fails because of failure to bind to the port (TIKA-3441).

  • Improve likelihood that tesseract will not be orphaned on jvm restart in tika-server (TIKA-3441).

  • Deprecate experimental PDFPreflightParser (TIKA-3437).

  • Apply encoding detection to zip entry names via Ryan421 (TIKA-3374).

... (truncated)

Commits
  • 79d724c [maven-release-plugin] prepare release 1.28.3-rc1
  • aba7414 Update CHANGES.txt for 1.28.3 release
  • 8d76590 tighten up regex in StandardsText
  • a454caf TIKA-3770 -- general upgrades for 1.28.3
  • fb721d6 Merge remote-tracking branch 'origin/branch_1x' into branch_1x
  • 9a5afd2 TIKA-3770: update jackson
  • ee9db0e TIKA-3770: remove entry that is also in parent pom.xml
  • 8dc66e5 TIKA-3770: revert update of jakarta.annotation-api, fails on jdk11+
  • 4009fc6 TIKA-3770: update lombok and jakarta.annotation-api
  • 7fd12a3 TIKA-3770: update zstd-jni
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.

dependabot[bot] avatar Sep 04 '25 15:09 dependabot[bot]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
15644213 Triggered Generic Password 57c6129c5a0643b419773859808cd810bf915c22 backend/src/main/resources/application.properties View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

gitguardian[bot] avatar Sep 22 '25 22:09 gitguardian[bot]