This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch 
dependabot/maven/com.azure-azure-sdk-bom-1.2.24
in repository https://gitbox.apache.org/repos/asf/camel.git


 discard c52c3e1bf2c Bump com.azure:azure-sdk-bom from 1.2.23 to 1.2.24
     add 95a358b1220 Bump jetty-version from 12.0.8 to 12.0.10 (#14315)
     add 990a3ae5a3d Revert "Bump jetty-version from 12.0.8 to 12.0.10 (#14315)"
     add 6813de54836 Bump jooq-version from 3.19.8 to 3.19.9 (#14333)
     add 123d3546e92 Bump org.redisson:redisson from 3.30.0 to 3.31.0 (#14325)
     add 2ae4ed78b54 Bump org.cometd.java:cometd-java-client-http-jetty from 
8.0.1 to 8.0.2 (#14326)
     add 73da4d7119f Bump gg.jte:jte from 3.1.10 to 3.1.12 (#14327)
     add f4d6d696134 Bump shiro-version from 2.0.0 to 2.0.1 (#14334)
     add f3f1a6b0ead Bump com.amazonaws:aws-xray-recorder-sdk-bom from 2.15.3 
to 2.16.0 (#14331)
     add 0b45bdd95ee Bump com.azure:azure-sdk-bom from 1.2.23 to 1.2.24

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   (c52c3e1bf2c)
            \
             N -- N -- N   
refs/heads/dependabot/maven/com.azure-azure-sdk-bom-1.2.24 (0b45bdd95ee)

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