This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/com.google.cloud-google-cloud-storage-2.61.0
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 67babf96926e chore(deps): Bump com.google.cloud:google-cloud-storage
add 3f4cc02ce62f chore(deps): Bump org.jgroups:jgroups from 5.5.1.Final to
5.5.2.Final (#20494)
add 65ab204d970a chore(deps): Bump
com.googlecode.libphonenumber:libphonenumber (#20490)
add 062adb0a57db chore(deps): Bump eu.maveniverse.maven.nisse:extension
(#20485)
add d3801ff1dec0 chore(deps): Bump redis.clients:jedis from 7.1.0 to 7.2.0
(#20486)
add 9e929896bdee chore(deps): Bump org.apache.xbean:xbean-spring from 4.28
to 4.29 (#20495)
add 5fe99f9c0891 chore(deps): Bump
com.google.cloud:google-cloud-aiplatform (#20484)
add a498254a73a9 chore(deps): Bump org.ow2.asm:asm-tree from 9.9 to 9.9.1
(#20492)
add 5e8769c29f61 chore(deps): Bump maven-resolver-version from 1.9.24 to
1.9.25 (#20497)
add 93c1ca3cdc7b chore(deps): Bump com.google.cloud:google-cloud-storage
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 (67babf96926e)
\
N -- N -- N
refs/heads/dependabot/maven/com.google.cloud-google-cloud-storage-2.61.0
(93c1ca3cdc7b)
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:
.mvn/extensions.xml | 2 +-
dsl/camel-jbang/camel-launcher/pom.xml | 2 +-
parent/pom.xml | 14 +++++++-------
3 files changed, 9 insertions(+), 9 deletions(-)
