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 ff66f25871 Upgrade Quarkus to 3.22.0.CR1
     add 5d6043a905 Regen SBOM from commit 
ded6523f9b68d2b1f4dfa85c482f5f9d6c15cd2f (#7139)
     new 5352f829cb Upgrade Quarkus to 3.22.0.CR1

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   (ff66f25871)
            \
             N -- N -- N   refs/heads/quarkus-main (5352f829cb)

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-quarkus-sbom/camel-quarkus-sbom.json | 28189 ++++++++++++++-------------
 camel-quarkus-sbom/camel-quarkus-sbom.xml  | 26276 +++++++++++++------------
 2 files changed, 28013 insertions(+), 26452 deletions(-)

Reply via email to