You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@archiva.apache.org by gi...@apache.org on 2022/06/06 23:23:15 UTC

[archiva-components] branch dependabot/maven/junit.jupiter.version-5.8.2 updated (2d18392 -> 35f5daa)

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

github-bot pushed a change to branch dependabot/maven/junit.jupiter.version-5.8.2
in repository https://gitbox.apache.org/repos/asf/archiva-components.git


 discard 2d18392  Bump junit.jupiter.version from 5.5.2 to 5.8.2
     add 649c173  Bump junit.platform.version from 1.5.2 to 1.8.2
     add 1f10394  Bump log4j.version from 2.17.1 to 2.17.2
     add 35f5daa  Bump junit.jupiter.version from 5.5.2 to 5.8.2

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   (2d18392)
            \
             N -- N -- N   refs/heads/dependabot/maven/junit.jupiter.version-5.8.2 (35f5daa)

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:
 pom.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)