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-pubsublite-1.15.7
in repository https://gitbox.apache.org/repos/asf/camel.git


 discard 016395e990d chore(deps): Bump com.google.cloud:google-cloud-pubsublite
     add 7a641d52c25 chore(deps): Bump aws-java-sdk2-version from 2.31.36 to 
2.31.37 (#17982)
     add ba202aed948 chore(deps): Bump com.google.cloud:google-cloud-storage 
(#17983)
     add 895192d717f chore(deps): Bump com.google.cloud:google-cloud-pubsub 
(#17985)
     add 82af0b1882f chore(deps): Bump com.azure:azure-storage-blob-changefeed 
(#17987)
     add 8889c9b71e7 chore(deps): Bump 
com.googlecode.libphonenumber:libphonenumber (#17988)
     add ddefad51ca9 chore(deps): Bump org.apache.fury:fury-core from 0.10.1 to 
0.10.2 (#17991)
     add ffae1c79888 chore(deps): Bump com.google.cloud:google-cloud-pubsublite

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   (016395e990d)
            \
             N -- N -- N   
refs/heads/dependabot/maven/com.google.cloud-google-cloud-pubsublite-1.15.7 
(ffae1c79888)

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 | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

Reply via email to