This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/github_actions/master/actions/setup-java-3.4.1
in repository https://gitbox.apache.org/repos/asf/archiva-redback-core.git
discard 1dd77aeb Bump actions/setup-java from 3.3.0 to 3.4.1
add a4aaec1e [MRM-2031] Switch to jdk 11
add 6ae17035 jdk11 as default
add 3f0924e4 fix spring upperbound version
add a83ae4ea Bump actions/setup-java from 3.3.0 to 3.4.1
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 (1dd77aeb)
\
N -- N -- N
refs/heads/dependabot/github_actions/master/actions/setup-java-3.4.1 (a83ae4ea)
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:
Jenkinsfile | 12 ++++++------
pom.xml | 15 +++++----------
.../apache/archiva/redback/users/AbstractUserManager.java | 5 ++---
3 files changed, 13 insertions(+), 19 deletions(-)
