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.160
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 95f422fd28e chore(deps): Bump huaweicloud-sdk-version from 3.1.159 to
3.1.160
add 75313fa902d chore(deps): Bump langchain4j-rc-version from 1.2.0 to
1.3.0 (#18847)
add dd8882b63aa chore(deps): Bump com.huaweicloud:esdk-obs-java from
3.25.5 to 3.25.7 (#18854)
add 63e6d52a1c4 chore(deps): Bump huaweicloud-sdk-version from 3.1.159 to
3.1.160
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 (95f422fd28e)
\
N -- N -- N
refs/heads/dependabot/maven/huaweicloud-sdk-version-3.1.160 (63e6d52a1c4)
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(-)
