This is an automated email from the ASF dual-hosted git repository.
apupier pushed a change to branch
dependabot/maven/com.azure-azure-sdk-bom-1.2.24
in repository https://gitbox.apache.org/repos/asf/camel.git
omit bb45ef92632 Bump com.azure:azure-sdk-bom from 1.2.23 to 1.2.24
add 37bfd87e444 Bump activemq-artemis-version from 2.33.0 to 2.34.0
(#14328)
add be4f248e401 Bump net.revelc.code:impsort-maven-plugin from 1.9.0 to
1.10.0 (#14330)
add 5f2da96d219 chore: adjust uploaded artifact configuration
add ba805c68ea7 Bump org.assertj:assertj-core from 3.25.3 to 3.26.0
add 219b6a804f3 Bump com.azure:azure-sdk-bom from 1.2.23 to 1.2.24
add 33a4890a71c chore: Upgrade test container azurite
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 (bb45ef92632)
\
N -- N -- N
refs/heads/dependabot/maven/com.azure-azure-sdk-bom-1.2.24 (33a4890a71c)
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:
.github/actions/component-test/action.yaml | 4 ++--
.github/actions/incremental-build/action.yaml | 2 +-
parent/pom.xml | 6 +++---
.../camel/test/infra/azure/common/services/container.properties | 2 +-
4 files changed, 7 insertions(+), 7 deletions(-)
