This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/huaweicloud-sdk-version-3.1.120
in repository https://gitbox.apache.org/repos/asf/camel.git
discard d606f53238c chore(deps): Bump huaweicloud-sdk-version from 3.1.119 to
3.1.120
add a9fee678fb4 chore(deps-dev): Bump com.networknt:json-schema-validator
(#16164)
add 91fdbee6f92 chore(deps): Bump bytebuddy-version from 1.15.7 to 1.15.10
(#16165)
add a88934f3c38 chore(deps): Bump org.mnode.ical4j:ical4j from 4.0.4 to
4.0.5 (#16166)
add 0e8ec2c3402 chore(deps): Bump activemq-artemis-version from 2.37.0 to
2.38.0 (#16167)
add efd5dd4cf1c chore(deps): Bump huaweicloud-sdk-version from 3.1.119 to
3.1.120
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 (d606f53238c)
\
N -- N -- N
refs/heads/dependabot/maven/huaweicloud-sdk-version-3.1.120 (efd5dd4cf1c)
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(-)
