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
discard 9691a4d8f2 Fixed azure due to version update
discard dc34a684a5 Fixed dropboc due to version change
discard a9726063b0 Add cli-connector support for Camel JBang runtime=quarkus
discard b7068f9c9d Revert "Disable microprofile-fault-tolerance testing due to
#5995"
discard fd8416a05a Upgrade Camel to 4.6.0
add 30fe04dc44 Regen SBOM from commit
0f7f3c0306a7e5cd574900a04d922b3a40674f10 (#6069)
new c3c90863db Upgrade Camel to 4.6.0
new 939e1a2e63 Revert "Disable microprofile-fault-tolerance testing due to
#5995"
new 4e153bda13 Add cli-connector support for Camel JBang runtime=quarkus
new 141ef98bcd Fixed dropboc due to version change
new 0c19627c33 Fixed azure due to version update
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 (9691a4d8f2)
\
N -- N -- N refs/heads/camel-main (0c19627c33)
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 5 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 | 1391 +++++++++++++++++++---------
camel-quarkus-sbom/camel-quarkus-sbom.xml | 693 +++++++++-----
2 files changed, 1431 insertions(+), 653 deletions(-)
