This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/com.amazonaws-aws-xray-recorder-sdk-bom-2.15.1
in repository https://gitbox.apache.org/repos/asf/camel.git
discard b3155a0d502 bump com.amazonaws:aws-xray-recorder-sdk-bom from 2.15.0
to 2.15.1
add ddcb29bafe1 Bump testcontainers-version from 1.19.5 to 1.19.6 (#13257)
add b3fb3d37e6a bump aws-java-sdk2-version from 2.24.7 to 2.24.8 (#13258)
add c73bd9b711b bump json-unit-version from 3.2.5 to 3.2.7 (#13260)
add e1014174ac1 bump org.springframework.batch:spring-batch-core from
5.1.0 to 5.1.1 (#13259)
add d0eb777760c bump com.amazonaws:aws-xray-recorder-sdk-bom from 2.15.0
to 2.15.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 (b3155a0d502)
\
N -- N -- N
refs/heads/dependabot/maven/com.amazonaws-aws-xray-recorder-sdk-bom-2.15.1
(d0eb777760c)
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 | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
