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 cc2e3c13cbc Regen for commit ce69c60ff41b48c5944721a058d1dd2b8763ab4f
add 85860555f8e CAMEL-18030 - Upgrade Jclouds to version 2.5.0
add 7bc0e61bc7b CAMEL-18030 - Upgrade Jclouds to version 2.5.0, aligning
the Guava version to 27.1-jre
add 6d16da075d1 Sync deps
add 905f736db9f Regen for commit 6d16da075d1849a775ab75e6209c3a539bbcc1f1
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 (cc2e3c13cbc)
\
N -- N -- N refs/heads/regen_bot (905f736db9f)
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 +++---
parent/pom.xml | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
