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 aa3a4ca Upgrade to Quarkus 2.8.0.CR1
add e783b84 Manage camel-quarkus-catalog in camel-quarkus-bom to allow
Camel K to use Quarkus Platform BOMs #3347
add ad3283f Require Maven 3.8.1+ to build Camel Quarkus
new 295e4a7 Upgrade to Quarkus 2.8.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 (aa3a4ca)
\
N -- N -- N refs/heads/quarkus-main (295e4a7)
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:
pom.xml | 2 +-
poms/bom/pom.xml | 5 +++++
2 files changed, 6 insertions(+), 1 deletion(-)
