This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/com.huaweicloud-esdk-obs-java-3.25.5
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 005467b069c chore(deps): Bump com.huaweicloud:esdk-obs-java from
3.25.4 to 3.25.5
add f5ef0aec1d7 chore(deps): Bump
com.google.auth:google-auth-library-oauth2-http (#18228)
add 6018a87ca43 chore(deps-dev): Bump com.graphql-java:graphql-java from
24.0 to 24.1 (#18230)
add 43411c343e3 chore(deps): Bump com.huaweicloud:esdk-obs-java from
3.25.4 to 3.25.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 (005467b069c)
\
N -- N -- N
refs/heads/dependabot/maven/com.huaweicloud-esdk-obs-java-3.25.5 (43411c343e3)
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 | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
