This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/com.azure-azure-sdk-bom-1.3.5
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 56b6d4e5bac7 chore(deps): Bump com.azure:azure-sdk-bom from 1.3.3 to
1.3.5
add ad2afa1c5f47 chore(camel-test-infra-kafka): upgrade
strimzi.container.image to 0.51.0-kafka-4.2.0 (#21816)
add 7386f677c080 chore(deps): Bump tools.jackson:jackson-bom from 3.0.3 to
3.1.0 (#21835)
add 2627e91426d1 chore(deps): Bump org.redisson:redisson from 3.52.0 to
4.3.0 (#21833)
add 5b4c4b199662 chore(deps): Bump jackson2-version from 2.20.2 to 2.21.1
(#21754)
add 90bd1327abdf chore(deps): Bump com.azure:azure-sdk-bom from 1.3.3 to
1.3.5
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 (56b6d4e5bac7)
\
N -- N -- N
refs/heads/dependabot/maven/com.azure-azure-sdk-bom-1.3.5 (90bd1327abdf)
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 | 6 +++---
.../org/apache/camel/test/infra/kafka/services/container.properties | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
