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/dompurify-3.4.12
in repository https://gitbox.apache.org/repos/asf/jena.git
discard b287016a39 Bump dompurify from 3.4.11 to 3.4.12 in
/jena-fuseki2/jena-fuseki-ui
add 101e93f302 Bump eslint from 10.6.0 to 10.7.0 in
/jena-fuseki2/jena-fuseki-ui
add 737a3ff307 Bump nanoid from 5.1.16 to 6.0.0 in
/jena-fuseki2/jena-fuseki-ui
add bbc47e5f49 Bump dompurify from 3.4.11 to 3.4.12 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 (b287016a39)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/jena-fuseki2/jena-fuseki-ui/dompurify-3.4.12
(bbc47e5f49)
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 | 2 +-
jena-fuseki2/jena-fuseki-ui/yarn.lock | 14 +++++++-------
2 files changed, 8 insertions(+), 8 deletions(-)
