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

slachiewicz pushed a change to branch agent/deprecation-main
in repository https://gitbox.apache.org/repos/asf/maven-resolver.git


    omit 2da475e15 Remove deprecation warnings from the main source sets (#2272)
    omit 64a107933 Move the HTTP test key material into SslTestSupport
     add 1e86df7c7 [MRESOLVER-2142] Probe random ports for the HTTP/3 test 
server
     add 5696308bc Extend ATR configuration in .asf.yaml
     add 9968f188b build(deps): bump com.google.guava:guava from 33.7.2-jre to 
33.8.0-jre (#2268)
     add 66eff1c04 Move the HTTP test key material into SslTestSupport
     add 42129ab6e Remove deprecation warnings from the main source sets (#2272)

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   (2da475e15)
            \
             N -- N -- N   refs/heads/agent/deprecation-main (42129ab6e)

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:
 .asf.yaml                                          |  3 +-
 .../aether/internal/test/util/http/HttpServer.java | 35 ++++++++++------------
 pom.xml                                            |  2 +-
 3 files changed, 18 insertions(+), 22 deletions(-)

Reply via email to