This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/aws.version-1.12.753
in repository https://gitbox.apache.org/repos/asf/tika.git
discard 4734a2269 Bump aws.version from 1.12.748 to 1.12.753
add 35426ce28 Bump com.nimbusds:nimbus-jose-jwt from 9.37.3 to 9.40
add 49f80bc0e Merge pull request #1841 from
apache/dependabot/maven/com.nimbusds-nimbus-jose-jwt-9.40
add 339dc5948 Bump org.apache.maven.plugins:maven-enforcer-plugin from
1.4.1 to 3.5.0
add e44107f5c Merge pull request #1833 from
apache/dependabot/maven/org.apache.maven.plugins-maven-enforcer-plugin-3.5.0
add ea9b128ef Bump aws.version from 1.12.748 to 1.12.753
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (4734a2269)
\
N -- N -- N refs/heads/dependabot/maven/aws.version-1.12.753
(ea9b128ef)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
tika-pipes/tika-fetchers/tika-fetcher-microsoft-graph/pom.xml | 2 +-
tika-pipes/tika-grpc/pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
