This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a change to branch regen_bot
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
discard e69d18277 Regen for commit f69d56d7d70b73f780f585f466ef988de73731b8
add 91e877b8f Fix #2984: run the Citrus itests against the Kamelets in
this working tree (#2987)
add 2442f40a7 Regen for commit 91e877b8f34a22ab70c89a0982de29599871084f
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 (e69d18277)
\
N -- N -- N refs/heads/regen_bot (2442f40a7)
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.
No new revisions were added by this update.
Summary of changes:
tests/camel-kamelets-itest/pom.xml | 2 ++
.../src/test/resources-filtered/citrus-application.properties | 7 +++++++
.../src/test/resources/mail/mail-sink-pipe.yaml | 5 +++++
3 files changed, 14 insertions(+)
