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 daf793f  Regen for commit 4099589ab43fde838dc111b04365c64499ebc18a
     add 8e6434d  Upgrade Kubernetes client and model to version 5.7.2
     add 7e286f5  Sync deps
     add 1e81d66  Regen for commit 34045738de92fc58eea935639468b46338d2b577
     add c9733d6  Regen for commit 1e81d66c24a646fffc6d9d24dba1abdc4e982c9f

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   (daf793f)
            \
             N -- N -- N   refs/heads/regen_bot (c9733d6)

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 | 4 ++--
 parent/pom.xml             | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

Reply via email to