This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/master/jjwt.version-0.11.5
in repository https://gitbox.apache.org/repos/asf/archiva-redback-core.git
discard 22cdcc53 Bump jjwt.version from 0.11.2 to 0.11.5
add cfcbcdf1 Bump actions/setup-java from 3.2.0 to 3.3.0
add f757ae2e Bump exec-maven-plugin from 1.6.0 to 3.0.0
add 167cf867 Bump maven-dependency-plugin from 3.2.0 to 3.3.0
add 4f68ddc3 Bump swagger-ui from 3.51.2 to 4.11.1
add c59fb99c move version properties in child or it is complicated to sync
and prevent dependabot working
add 11ad1715 Bump jjwt.version from 0.11.2 to 0.11.5
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 (22cdcc53)
\
N -- N -- N
refs/heads/dependabot/maven/master/jjwt.version-0.11.5 (11ad1715)
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 | 41 ++++++++++++++++++++--
.../redback-rest/redback-rest-services/pom.xml | 2 +-
3 files changed, 41 insertions(+), 4 deletions(-)
