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 a6028335f02 Regen for commit 5c94dbe2a3aef93eb4140b54f54ad275ddbe94b8
add c6dc3f27d90 Upgrade Pulsar to version 2.11.0
add 0b56e2e87ad Use latest container image for Pulsar 2.11.0
add 70efc74c0d4 Regen
add 8698ee65e4d Regen for commit 70efc74c0d424be018db77f484955c04702863af
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 (a6028335f02)
\
N -- N -- N refs/heads/regen_bot (8698ee65e4d)
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 | 2 +-
parent/pom.xml | 2 +-
.../camel/test/infra/pulsar/services/PulsarLocalContainerService.java | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
