This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.apache.maven.plugins-maven-enforcer-plugin-3.6.0
in repository https://gitbox.apache.org/repos/asf/wicket.git
discard fbf45aab26 Bump org.apache.maven.plugins:maven-enforcer-plugin from
3.1.0 to 3.6.0
add c95316207e Bump org.checkerframework:checker-qual from 3.49.4 to
3.49.5 (#1205)
add 59ee207172 Bump org.apache.maven.plugins:maven-gpg-plugin from 3.2.7
to 3.2.8 (#1204)
add 1bf31b7bf5 Bump junit.version from 5.13.2 to 5.13.3 (#1202)
add 73cdfaf97f Bump org.apache.maven.plugins:maven-enforcer-plugin from
3.1.0 to 3.6.0
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 (fbf45aab26)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.maven.plugins-maven-enforcer-plugin-3.6.0
(73cdfaf97f)
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 ++--
wicket-migration/pom.xml | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
