This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regen_bot
in repository https://gitbox.apache.org/repos/asf/camel.git.
discard 311d4d0 Regen for commit d76116e92eda974c76de1460d81deb2924385e5b
add c52fd64 [CAMEL-16962]tests in camel-flink failed with JDK17
add b5f3306 Merge branch 'main' of github.com:apache/camel into main
add 94ad6a8 Regen for commit b5f330679fa372981620a81cb2621f81baeb2ad8
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 (311d4d0)
\
N -- N -- N refs/heads/regen_bot (94ad6a8)
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:
components/camel-flink/pom.xml | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
