This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/metrics.version-4.2.25
in repository https://gitbox.apache.org/repos/asf/wicket.git
omit b7798bc060 Bump metrics.version from 4.2.24 to 4.2.25
add 97fe7ae12f Bump org.openrewrite.recipe:rewrite-recipe-bom from 2.6.2
to 2.6.3 (#779)
add d909e8574f Bump
org.primefaces.extensions:resources-optimizer-maven-plugin (#778)
add e7b4c2b1f4 Bump org.mockito:mockito-core from 5.9.0 to 5.10.0 (#777)
add 683335f469 Bump metrics.version from 4.2.24 to 4.2.25
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 (b7798bc060)
\
N -- N -- N refs/heads/dependabot/maven/metrics.version-4.2.25
(683335f469)
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(-)
