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/npm-patch-group-bff5ba33ca
in repository https://gitbox.apache.org/repos/asf/jena.git
discard c886dcda6b Bump the npm-patch-group group
add f19d5a729a Bump vite from 5.2.13 to 5.3.1 in
/jena-fuseki2/jena-fuseki-ui
add 686b0e601b Bump cypress from 13.11.0 to 13.12.0 in
/jena-fuseki2/jena-fuseki-ui
add a8b616ceab Bump @eslint/js from 9.4.0 to 9.5.0 in
/jena-fuseki2/jena-fuseki-ui
add 8f7beecbe8 Bump the npm-patch-group group
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 (c886dcda6b)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/jena-fuseki2/jena-fuseki-ui/npm-patch-group-bff5ba33ca
(8f7beecbe8)
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/yarn.lock | 302 +++++++++++++++++-----------------
1 file changed, 151 insertions(+), 151 deletions(-)
