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/js-yaml-3.15.1
in repository https://gitbox.apache.org/repos/asf/jena.git
omit 9f77f491c7 Bump js-yaml from 3.14.2 to 3.15.1 in
/jena-fuseki2/jena-fuseki-ui
add 015cb22e89 Git setup for yarn modern
add 51f380478b Bump js-yaml from 3.14.2 to 3.15.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 (9f77f491c7)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/jena-fuseki2/jena-fuseki-ui/js-yaml-3.15.1
(51f380478b)
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:
.gitattributes | 3 ++-
.../auth-jdk-passwd => jena-fuseki-ui/.gitattributes} | 4 +++-
jena-fuseki2/jena-fuseki-ui/.gitignore | 9 +++++++++
jena-fuseki2/jena-fuseki-ui/.yarn/install-state.gz | Bin 821926 -> 0 bytes
4 files changed, 14 insertions(+), 2 deletions(-)
copy jena-fuseki2/{jena-fuseki-main/testing/Access/auth-jdk-passwd =>
jena-fuseki-ui/.gitattributes} (59%)
delete mode 100644 jena-fuseki2/jena-fuseki-ui/.yarn/install-state.gz
