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
omit f09dac69824 Regen for commit 23c55596f5df0246c354a4fa02c3afe1a86c9845
add 28e10442aeb Upgrade Flink to version 1.15.0
add 12cd6ca616f Sync deps
add e42f5d810ad Upgrade Netty to version 4.1.77.Final
add 5a86ee208ac Sync deps
add 4c59ae47021 Upgrade Netty Boring SSL to version 2.0.52.Final
add fb7e7fb50a0 Sync deps
add 1831a9ee0b8 Regen for commit fb7e7fb50a0581b6fada197af6af628aa78be529
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 (f09dac69824)
\
N -- N -- N refs/heads/regen_bot (1831a9ee0b8)
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:
camel-dependencies/pom.xml | 6 +++---
components/camel-flink/pom.xml | 4 ++--
parent/pom.xml | 6 +++---
3 files changed, 8 insertions(+), 8 deletions(-)
