This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a change to branch tika-2.9.1
in repository https://gitbox.apache.org/repos/asf/camel.git
discard efd4714e022 Upgrade Tika to version 2.9.1
omit 20d0a24fecc Upgrade AWS SDK v2 to version 2.21.10
add 3f05ab5f77b Upgrade AWS SDK v2 to version 2.21.10 (#11857)
add 69e403a12b6 CAMEL-20049: camel-activemq - Upgrade to latest releases
add 36af6a699f7 Regen SBOM from commit
69e403a12b6a2678d544cf346afe4586de252c74 (#11859)
new 879917073ce Upgrade Tika to version 2.9.1
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 (efd4714e022)
\
N -- N -- N refs/heads/tika-2.9.1 (879917073ce)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
camel-sbom/camel-sbom.json | 4880 ++++++++++++++++++++++----------------------
camel-sbom/camel-sbom.xml | 4698 +++++++++++++++++++++---------------------
parent/pom.xml | 2 +-
3 files changed, 4740 insertions(+), 4840 deletions(-)
