This is an automated email from the ASF dual-hosted git repository.
jiriondrusek pushed a change to branch camel-main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
discard 853ac54190 Upgrade Camel to 4.17.0
discard 47c3193f7a Workaroound because of #7942
discard 76341aeb0c Enable okhttp 5.x to coexist with 4.x
discard 701f450003 Upgrade Camel to 4.16.0
discard eb124ae8ce Generates certificates for cxf security tests
add be98edb0b7 Generates certificates for cxf security tests (#7945)
new 7976613a47 Upgrade Camel to 4.16.0
new be6c00e534 Enable okhttp 5.x to coexist with 4.x
new c025a5ece9 Workaroound because of #7942
new 46a52ea968 Upgrade Camel to 4.17.0
new 076f7901ba Generated files
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 (853ac54190)
\
N -- N -- N refs/heads/camel-main (076f7901ba)
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 5 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:
.../aws-xray/runtime/src/main/resources/META-INF/quarkus-extension.yaml | 1 +
.../stomp/runtime/src/main/resources/META-INF/quarkus-extension.yaml | 1 +
2 files changed, 2 insertions(+)
