This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch quarkus-master
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git.
discard ed4ab98 Azure extension native build fails with Quarkus 1.13 #2299
discard f4941f0 Fix #1918 to add a integration test with camel-jdbc and
camel-jms
discard 71dbac7 Remove support for Webocket JSR 356
discard d5871ff Upgrade to Quarkus 1.13.0.Final
add cb23ff7 Updated CHANGELOG.md
new f464519 Upgrade to Quarkus 1.13.0.Final
new a7a83a5 Remove support for Webocket JSR 356
new eda54f7 Fix #1918 to add a integration test with camel-jdbc and
camel-jms
new bd626d4 Azure extension native build fails with Quarkus 1.13 #2299
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 (ed4ab98)
\
N -- N -- N refs/heads/quarkus-master (bd626d4)
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 4 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:
CHANGELOG.md | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
