This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/com.hazelcast-hazelcast-5.4.0
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 536f5b74998 Bump com.hazelcast:hazelcast from 5.3.7 to 5.4.0
add f89d0039463 Bump com.alibaba:fastjson from 2.0.50 to 2.0.51
add 6c1d73fbf63 Bump io.smallrye.config:smallrye-config from 3.8.1 to 3.8.2
add 00c342df7bb Bump commons-validator:commons-validator from 1.8.0 to
1.9.0
add cbefcf750fa Bump io.atlassian.fugue:fugue from 5.0.0 to 5.0.1
add b25904bd13c Bump org.hsqldb:hsqldb from 2.7.2 to 2.7.3
add 1e2b129b34f Bump commons-net:commons-net from 3.10.0 to 3.11.0
add 5b85a4b70db Bump org.hdrhistogram:HdrHistogram from 2.2.1 to 2.2.2
add 57f738760f7 Bump com.hazelcast:hazelcast from 5.3.7 to 5.4.0
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 (536f5b74998)
\
N -- N -- N
refs/heads/dependabot/maven/com.hazelcast-hazelcast-5.4.0 (57f738760f7)
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:
parent/pom.xml | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
