This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.elasticsearch.client-elasticsearch-rest-client-sniffer-8.17.3
in repository https://gitbox.apache.org/repos/asf/camel.git
discard e6a132433ce chore(deps): Bump
org.elasticsearch.client:elasticsearch-rest-client-sniffer
add b8319d58361 Bump jbang versions
add 25b49c54629 upgrade jbang
add a2932ef0425 chore(deps): Bump testcontainers-version from 1.20.5 to
1.20.6 (#17355)
add 19980fe4122 chore(deps): Bump aws-java-sdk2-version from 2.30.32 to
2.30.33 (#17356)
add 76ad3ff3c29 chore(deps): Bump grpc-version from 1.70.0 to 1.71.0
(#17357)
add 78cb4a2f431 chore(deps): Bump elasticsearch-java-client-version
(#17358)
add 6d2cd0a5389 chore(deps): Bump
org.elasticsearch.client:elasticsearch-rest-client-sniffer
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 (e6a132433ce)
\
N -- N -- N
refs/heads/dependabot/maven/org.elasticsearch.client-elasticsearch-rest-client-sniffer-8.17.3
(6d2cd0a5389)
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:
dsl/camel-jbang/camel-jbang-container/Dockerfile | 6 +++---
dsl/camel-jbang/camel-jbang-main/dist/CamelJBang.java | 4 ++--
.../camel-jbang-main/src/main/jbang/main/CamelJBang.java | 4 ++--
parent/pom.xml | 8 ++++----
4 files changed, 11 insertions(+), 11 deletions(-)
