This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/npm_and_yarn/jena-fuseki2/jena-fuseki-ui/babel/core-8.0.1
in repository https://gitbox.apache.org/repos/asf/jena.git
discard 92ef937015 Bump @babel/core from 7.29.7 to 8.0.1 in
/jena-fuseki2/jena-fuseki-ui
add a9af2a4d9f GH-4185: Force the dependency of jspecify
add 2192ab5382 Bump the npm-patch-group group
add 67daa5be3e Bump eslint from 10.8.1 to 10.9.1 in
/jena-fuseki2/jena-fuseki-ui
add e9005ee971 Bump @babel/core from 7.29.7 to 8.0.1 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 (92ef937015)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/jena-fuseki2/jena-fuseki-ui/babel/core-8.0.1
(e9005ee971)
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:
.../sparql/engine/benchmark/QueryTaskResult.java | 3 -
.../org/apache/jena/mem/collection/JenaSet.java | 9 +-
jena-fuseki2/jena-fuseki-ui/package.json | 2 +-
jena-fuseki2/jena-fuseki-ui/yarn.lock | 188 +++++++++++----------
pom.xml | 20 ++-
5 files changed, 123 insertions(+), 99 deletions(-)
