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 fb133df194 Fix Debezium native support
omit 41195dcb2b Fixed zipfile (compression test)
omit 5e093c2404 Upgrade Debezium to 3.2.1.Final
omit 6d6bd3a2e2 Regen files
omit d7a75fd21a Fixed compilation error of BuildTimeJsonSchemaResolver
omit a0a04feb96 Gen files
omit a18b7e0399 Gen files
omit 404d185f84 Upgrade debezium to 3.2.0.Final
omit 7e2865e036 Gen files
omit 7af2aacceb Redefined mariadb devservice to use mirror.gcr.io/* instead
of docker.io/*
omit ac41bbed62 Gen files
omit 857262cb09 Gen files
omit 5ad18d0184 Fixed azure grouped tests
omit a444d34522 regen files
omit d230fd07d1 Gen files
omit 3dccfecd11 gen files
omit dd01006ef1 Added await into spring-rebbitmq to see result on CI
omit 0dd7ae5559 Fixed compilation issue
omit c5e1320dcf Upgrade Camel to 4.14.0
omit b3cb336e21 Add iso8583 extension
add 57dd177dae Bump quarkiverse-langchain4j.version from 1.1.0 to 1.1.1
new 4ec8ea39cf Add iso8583 extension
new 87c24ad022 Upgrade Camel to 4.14.0
new cd0da9de53 Fixed compilation issue
new 9f410d9469 Added await into spring-rebbitmq to see result on CI
new b066789973 gen files
new 5265510b22 Gen files
new 6235de7558 regen files
new 611290e193 Fixed azure grouped tests
new c26a71cce0 Gen files
new 91c50ffa2c Gen files
new 86b66f55d9 Redefined mariadb devservice to use mirror.gcr.io/* instead
of docker.io/*
new 22a26d3043 Gen files
new 023c23b871 Upgrade debezium to 3.2.0.Final
new 3770f8a68a Gen files
new d9e6719ed2 Gen files
new 595ad1b604 Fixed compilation error of BuildTimeJsonSchemaResolver
new 8b7dc4a7a4 Regen files
new 3ce3628521 Upgrade Debezium to 3.2.1.Final
new 51db3bf46c Fixed zipfile (compression test)
new 27593e486b Fix Debezium native support
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 (fb133df194)
\
N -- N -- N refs/heads/camel-main (27593e486b)
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 20 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/src/main/generated/flattened-full-pom.xml | 4 ++--
poms/bom/src/main/generated/flattened-reduced-pom.xml | 4 ++--
poms/bom/src/main/generated/flattened-reduced-verbose-pom.xml | 4 ++--
4 files changed, 7 insertions(+), 7 deletions(-)
