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 9a6e3cca73 Upgrade Camel to 3.20.0
discard 9999d8e849 Adding into CI build of investigation purposes
discard 999e8c8f86 Disabled FaultTolerance test because of issues 4298
discard ca54555963 Fix #4216 to make xml integration tests working in native
build (#4217)
add 30520e877f Update index.adoc
add 29c52e0dae Updated CHANGELOG.md
new f3b4423280 Fix #4216 to make xml integration tests working in native
build (#4217)
new a5acddbb0c Disabled FaultTolerance test because of issues 4298
new 30965e399f Adding into CI build of investigation purposes
new 6358ca2654 Upgrade Camel to 3.20.0
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 (9a6e3cca73)
\
N -- N -- N refs/heads/camel-main (6358ca2654)
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 | 1 +
docs/modules/ROOT/pages/index.adoc | 4 ++--
2 files changed, 3 insertions(+), 2 deletions(-)