[archiva-redback-core] branch dependabot/maven/redback-2.6.x/springVersion-5.3.20 updated (8594ea06 -> e8d12442)

[gi...@apache.org]

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

github-bot pushed a change to branch dependabot/maven/redback-2.6.x/springVersion-5.3.20
in repository https://gitbox.apache.org/repos/asf/archiva-redback-core.git


 discard 8594ea06 Bump springVersion from 4.2.1.RELEASE to 5.3.20
     add 63ac0a99 Bump plexus-interpolation from 1.9 to 1.26
     add 37692026 Bump actions/setup-java from 3.2.0 to 3.3.0
     add cc108fe9 Bump commons-codec from 1.6 to 1.15
     add 85f263ac Bump plexus-utils from 3.0 to 3.4.2
     add aba7511b Bump xalan from 2.7.0 to 2.7.2
     add 5c123e05 Bump log4j2Version from 2.17.1 to 2.17.2
     add d6e24c11 Bump guava from 13.0.1 to 23.0
     add a591ee1f Bump assertj-core from 1.7.1 to 3.23.1
     add e8d12442 Bump springVersion from 4.2.1.RELEASE to 5.3.20

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   (8594ea06)
            \
             N -- N -- N   refs/heads/dependabot/maven/redback-2.6.x/springVersion-5.3.20 (e8d12442)

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:
 .github/workflows/maven.yml |  2 +-
 pom.xml                     | 12 ++++++------
 2 files changed, 7 insertions(+), 7 deletions(-)