This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.bouncycastle-bcprov-jdk18on-1.80
in repository https://gitbox.apache.org/repos/asf/wicket.git
omit 38f6aa3e49 Bump org.bouncycastle:bcprov-jdk18on from 1.79 to 1.80
add 4b2f365dcf Bump org.assertj:assertj-core from 3.27.2 to 3.27.3 (#1086)
add 8b07062fd7 Bump io.micrometer:micrometer-core from 1.14.1 to 1.14.3
(#1085)
add efe1ae57d5 Bump spring.version from 6.2.1 to 6.2.2 (#1084)
add 2b868bebd2 Bump org.bouncycastle:bcprov-jdk18on from 1.79 to 1.80
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 (38f6aa3e49)
\
N -- N -- N
refs/heads/dependabot/maven/org.bouncycastle-bcprov-jdk18on-1.80 (2b868bebd2)
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(-)
