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/zazuko/yasqe-4.3.0
in repository https://gitbox.apache.org/repos/asf/jena.git
discard bbafa3f47a Bump @zazuko/yasqe from 4.2.34 to 4.3.0 in
/jena-fuseki2/jena-fuseki-ui
add b37369f83a Bump the maven-patch-group group with 3 updates
add aff9af9f7a Bump commons-cli:commons-cli from 1.6.0 to 1.7.0
add 11dae70466 Bump the npm-patch-group group
add 300b4e8527 Bump cypress from 13.7.3 to 13.8.0 in
/jena-fuseki2/jena-fuseki-ui
add 61c8f51e0a Bump @zazuko/yasqe from 4.2.34 to 4.3.0 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 (bbafa3f47a)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/jena-fuseki2/jena-fuseki-ui/zazuko/yasqe-4.3.0
(61c8f51e0a)
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 | 200 +++++++++++++++++-----------------
pom.xml | 6 +-
2 files changed, 104 insertions(+), 102 deletions(-)
