This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/maven/org.cometd.java-cometd-java-client-http-jetty-9.0.1
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 8289037c7f20 chore(deps-dev): Bump
org.cometd.java:cometd-java-client-http-jetty
add a8536b53f659 chore(deps): Bump org.opensearch.client:opensearch-java
add 75738569a514 chore(deps): Bump io.camunda:zeebe-client-java from 8.9.7
to 8.9.8
add d4bc4041fb3e chore(deps): Bump io.dapr:dapr-sdk from 1.17.2 to 1.18.0
add 1fd8cba2c3e6 chore(deps): Bump mima-version from 2.4.45 to 2.4.46
add eabdb059694f chore(deps): Bump cometd-java-server-version from 9.0.0
to 9.0.1
add ee8445b315f5 chore(deps): Bump org.eclipse.jgit:org.eclipse.jgit
add d8cc6250d78c chore(deps): Bump cxf-version from 4.2.1 to 4.2.2
add 1747029774df chore(deps): Bump io.camunda:camunda-client-java from
8.9.7 to 8.9.8
add e3376e28b86a chore(deps-dev): Bump
org.cometd.java:cometd-java-client-http-jetty
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 (8289037c7f20)
\
N -- N -- N
refs/heads/dependabot/maven/org.cometd.java-cometd-java-client-http-jetty-9.0.1
(e3376e28b86a)
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 | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
