This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/npm_and_yarn/jena-fuseki2/jena-fuseki-ui/multi-ca8c3291f3
in repository https://gitbox.apache.org/repos/asf/jena.git
discard a69b31560d Bump vitest and @vitest/coverage-v8 in
/jena-fuseki2/jena-fuseki-ui
add 1705c2e323 Bump eslint-plugin-promise in /jena-fuseki2/jena-fuseki-ui
add c256985a60 GH-2611: Add --pool=threads to vitest run
add 46b266c97a Bump vitest and @vitest/coverage-v8 in
/jena-fuseki2/jena-fuseki-ui
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 (a69b31560d)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/jena-fuseki2/jena-fuseki-ui/multi-ca8c3291f3
(46b266c97a)
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:
jena-fuseki2/jena-fuseki-ui/package.json | 4 ++--
jena-fuseki2/jena-fuseki-ui/yarn.lock | 7 ++++++-
2 files changed, 8 insertions(+), 3 deletions(-)
