This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a change to branch dependabot/maven/kudu-version-1.18.1
in repository https://gitbox.apache.org/repos/asf/camel.git
discard fb475bd15fc5 chore(deps): Bump kudu-version from 1.18.0 to 1.18.1
add b25daa7eb32f chore(deps): Bump aws-java-sdk2-version from 2.41.1 to
2.41.2
add 13ad863f6973 chore(deps): Bump com.arangodb:arangodb-java-driver
add 60f141db067c chore(deps): Bump com.cedarsoftware:java-util from 4.72.0
to 4.80.0 (#20693)
add 2ebdb4822a8d chore(deps): Bump kudu-version from 1.18.0 to 1.18.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 (fb475bd15fc5)
\
N -- N -- N refs/heads/dependabot/maven/kudu-version-1.18.1
(2ebdb4822a8d)
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(-)
