This is an automated email from the ASF dual-hosted git repository.
reiern70 pushed a change to branch reiern70/crsf
in repository https://gitbox.apache.org/repos/asf/wicket.git
discard 7bc5a3ab45 [WICKET-7161] add a CSRF
token-generating-including-checking form
add bee4cfef8e Bump on-headers and morgan in /testing/wicket-js-tests
(#1210)
add 12be2efee2 Bump junit.version from 5.13.3 to 5.13.4 (#1218)
add 7bca679352 Bump com.google.errorprone:error_prone_annotations from
2.40.0 to 2.41.0 (#1216)
add 732f75b499 Bump org.apache.commons:commons-text from 1.13.1 to 1.14.0
(#1217)
add 2d8e051076 Bump commons-io:commons-io from 2.19.0 to 2.20.0 (#1213)
add ff46f5aa02 Bump spring.version from 6.2.8 to 6.2.9 (#1212)
add ebfd87c5c7 Bump io.micrometer:micrometer-core from 1.15.1 to 1.15.2
(#1211)
add 24156ed023 [WICKET-7161] add a CSRF
token-generating-including-checking form
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 (7bc5a3ab45)
\
N -- N -- N refs/heads/reiern70/crsf (24156ed023)
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 | 8 ++++----
testing/wicket-js-tests/package-lock.json | 16 +++++++++-------
wicket-migration/pom.xml | 4 ++--
3 files changed, 15 insertions(+), 13 deletions(-)
