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.17.0
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 212449d6fe2 chore(deps): Bump com.amazonaws:aws-xray-recorder-sdk-bom
add 82e3e8dc4e7 chore(deps): Bump aws-java-sdk2-version from 2.26.19 to
2.26.20 (#14811)
add 448d7990557 chore(deps): Bump elasticsearch-java-client-version
(#14812)
add 8cc71dd02a1 chore(deps): Bump
com.google.apis:google-api-services-drive (#14813)
add 5ef0b65b77f chore(deps): Bump com.amazonaws:aws-xray-recorder-sdk-bom
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 (212449d6fe2)
\
N -- N -- N
refs/heads/dependabot/maven/com.amazonaws-aws-xray-recorder-sdk-bom-2.17.0
(5ef0b65b77f)
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 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
