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 0679de23698 Regen for commit 3c5b5fa62bc07204adbc9e72b8b63f049a1bcf96
add ab649213da0 (chores) camel-aws2-kinesis: fixed readiness health check
add 174576494d6 Regen for commit ab649213da0e0e6e74d29d632c973151570e4888
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 (0679de23698)
\
N -- N -- N refs/heads/regen_bot (174576494d6)
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:
.../main/camel-main-configuration-metadata.json | 2 +
.../apache/camel/catalog/schemas/camel-spring.xsd | 9692 +++++++-------------
.../Kinesis2ConsumerHealthCustomClientIT.java | 20 +-
3 files changed, 3474 insertions(+), 6240 deletions(-)
