This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch camel-main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
omit 98d71effeb geerated poms
omit 698f5e33ec generated files
omit 926893362f generated poms
omit a224ba13ba generated poms
omit 2d55b005c0 Disable MicroProfile Fault Tolerance tests due to #6285
omit d441ac1600 Upgrade Camel to 4.8.0
add a25fe867cd Regen SBOM from commit
1a39ebb8d612cbbea0c96a4bc517ddff59cf08ad (#6317)
new dd42eee0cf Upgrade Camel to 4.8.0
new 4014a796db Disable MicroProfile Fault Tolerance tests due to #6285
new cbd1f26e49 generated poms
new 77315c627d generated poms
new 58af01783b generated files
new 9587b1aa56 geerated poms
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 (98d71effeb)
\
N -- N -- N refs/heads/camel-main (9587b1aa56)
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 6 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-quarkus-sbom/camel-quarkus-sbom.json | 1940 ++++++++++++++--------------
camel-quarkus-sbom/camel-quarkus-sbom.xml | 1672 ++++++++++++------------
2 files changed, 1808 insertions(+), 1804 deletions(-)
