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 06dd2bed80 Upgrade Camel to 3.20.0
discard 982f679c1d Fix #4216 to make xml integration tests working in native
build (#4217)
add 0f06fbd714 Updated CHANGELOG.md
add ba608351df Remove camel-quarkus-support-xstream from salesforce
extension issue #4272 .
new 5c2462e3ec Fix #4216 to make xml integration tests working in native
build (#4217)
new f8030e1219 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 (06dd2bed80)
\
N -- N -- N refs/heads/camel-main (f8030e1219)
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 2 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 | 3 +++
extensions/salesforce/deployment/pom.xml | 4 ----
extensions/salesforce/runtime/pom.xml | 4 ----
3 files changed, 3 insertions(+), 8 deletions(-)
