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 93f8ee1edf4 Regen for commit 7fb98e9b1900c478f7ca97b26b18a5f02f4cabe6
add 83c42784f05 CAMEL-18287 - Camel-AWS Eventbridge: Support operation
putEvents to send custom event to Eventbridge
add 66b0777773a CAMEL-18287 - Camel-AWS Eventbridge: Support operation
putEvents to send custom event to Eventbridge
add 38a59a7a317 Regen for commit 66b0777773aac7e6604822f0148643c3d41d54e8
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 (93f8ee1edf4)
\
N -- N -- N refs/heads/regen_bot (38a59a7a317)
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:
.../aws2/eventbridge/EventbridgeProducer.java | 25 +++++++++++++++++++++-
1 file changed, 24 insertions(+), 1 deletion(-)
