This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/mcp-java-sdk-version-1.1.0
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 41d2dfea42e1 chore(deps): Bump mcp-java-sdk-version from 1.0.0 to 1.1.0
add a46bb3c97a09 CAMEL-23112 - add back JDk 17 on Jenkins
add 23ef07cc875a chore(deps): Bump aws-java-sdk2-version from 2.42.14 to
2.42.15 (#22063)
add 8c275539f7bb chore(deps): Bump grpc-version from 1.79.0 to 1.80.0
add c5f217dc8973 chore(deps): Bump hapi-fhir-version from 8.8.0 to 8.8.1
add 9869511dc794 chore(deps): Bump com.ibm.icu:icu4j from 78.2 to 78.3
add 7205581ea12a chore(deps): Bump com.openai:openai-java from 4.28.0 to
4.29.0
add bed56a3e9f04 chore(deps): Bump mcp-java-sdk-version from 1.0.0 to 1.1.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 (41d2dfea42e1)
\
N -- N -- N
refs/heads/dependabot/maven/mcp-java-sdk-version-1.1.0 (bed56a3e9f04)
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:
Jenkinsfile | 24 ++++++++++++++++++++++--
Jenkinsfile.deploy | 2 +-
Jenkinsfile.jbangtest | 2 +-
parent/pom.xml | 10 +++++-----
4 files changed, 29 insertions(+), 9 deletions(-)
