This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/npm_and_yarn/testing/wicket-js-tests/grunt-contrib-nodeunit-5.0.0
in repository https://gitbox.apache.org/repos/asf/wicket.git
discard a82bc950fa Bump grunt-contrib-nodeunit in /testing/wicket-js-tests
add 18b386b88a Bump org.aspectj:aspectjrt from 1.9.19 to 1.9.20.1 (#620)
add fe8ca9c20b Bump jakarta.transaction:jakarta.transaction-api from 2.0.0
to 2.0.1 (#613)
add e9e986bf98 Bump grunt-contrib-connect in /testing/wicket-js-tests
(#611)
add 76bdc16f50 Bump grunt-contrib-qunit from 7.0.0 to 7.0.1 in
/testing/wicket-js-tests (#609)
add f3043b3c73 Bump grunt-contrib-nodeunit in /testing/wicket-js-tests
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 (a82bc950fa)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/testing/wicket-js-tests/grunt-contrib-nodeunit-5.0.0
(f3043b3c73)
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 | 2 +-
testing/wicket-common-tests/pom.xml | 2 +-
testing/wicket-js-tests/package-lock.json | 142 ++++++++++++++++++++----------
testing/wicket-js-tests/package.json | 4 +-
4 files changed, 99 insertions(+), 51 deletions(-)
