[camel] branch regen_bot_3x updated (57851045563 -> daa2a16f1a1)

[gi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch regen_bot_3x
in repository https://gitbox.apache.org/repos/asf/camel.git


    omit 57851045563 Regen for commit 8f0d6253763b1db91e0c45287c5abd5bd7fbf1ca
     add 30730d0b8d1 Regen
     add 77c8fcc0ca7 Regen for commit 8f0d6253763b1db91e0c45287c5abd5bd7fbf1ca (#10898)
     add 9fb67318f7b Regen for commit 8f0d6253763b1db91e0c45287c5abd5bd7fbf1ca (#10899)
     add 999a34548ea Update camel releases in camel-catalog
     add daa2a16f1a1 Regen for commit 999a34548eaba8ac0d17d8bdd4285f9bcfe4a047

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   (57851045563)
            \
             N -- N -- N   refs/heads/regen_bot_3x (daa2a16f1a1)

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:
 .../resources/org/apache/camel/catalog/releases/camel-releases.json | 6 ++++++
 1 file changed, 6 insertions(+)