This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/com.box-box-java-sdk-4.16.1
in repository https://gitbox.apache.org/repos/asf/camel.git
discard ac9e44dd067 chore(deps): Bump com.box:box-java-sdk from 4.16.0 to
4.16.1
add 962c6281def CAMEL-21956: camel-jbang - k8s plugin does not delete the
ingress (#17918)
add 71092537932 chore(deps): Bump aws-java-sdk2-version from 2.31.31 to
2.31.32 (#17920)
add 23b63876c41 chore(deps): Bump com.pubnub:pubnub-gson from 10.4.7 to
10.5.0 (#17921)
add fcf976f4a4a chore(deps): Bump activemq-artemis-version from 2.40.0 to
2.41.0 (#17922)
add 18df30d16fe CAMEL-22034: Upgrade to Bouncycastle 1.80 (#17924)
add b6a83bbd6c9 chore(deps): Bump com.dylibso.chicory:runtime from 1.2.1
to 1.3.0 (#17925)
add c500c537106 chore(deps): Bump com.box:box-java-sdk from 4.16.0 to
4.16.1
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 (ac9e44dd067)
\
N -- N -- N
refs/heads/dependabot/maven/com.box-box-java-sdk-4.16.1 (c500c537106)
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:
components/camel-as2/camel-as2-api/pom.xml | 11 ++++++-----
.../core/commands/kubernetes/KubernetesDelete.java | 23 ++++++++++++++--------
parent/pom.xml | 10 +++++-----
3 files changed, 26 insertions(+), 18 deletions(-)
