This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch quarkus-main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
discard d0d5b3d87c Disable Micrometer JMX tests due to #6984
discard 9bdc1a0f88 Upgrade Quarkus to 3.19.0.CR1
add ed83516e7c Regen SBOM from commit
4d74a7d8973d52ba1ee21d4c3037f18ea88b7b51 (#6987)
new 8ed3d48ba1 Upgrade Quarkus to 3.19.0.CR1
new 44c6e4b1f8 Disable Micrometer JMX tests due to #6984
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 (d0d5b3d87c)
\
N -- N -- N refs/heads/quarkus-main (44c6e4b1f8)
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 2 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 | 2024 ++++++++++++++--------------
camel-quarkus-sbom/camel-quarkus-sbom.xml | 1240 ++++++++---------
2 files changed, 1640 insertions(+), 1624 deletions(-)
