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/eslint-plugin-promise-6.6.0
in repository https://gitbox.apache.org/repos/asf/jena.git
discard 53a2590237 Bump eslint-plugin-promise in /jena-fuseki2/jena-fuseki-ui
add b08d6f0f92 Bump the npm-patch-group group
add 8fee53eb46 Bump @vitejs/plugin-vue in /jena-fuseki2/jena-fuseki-ui
add 579f5629c7 Bump eslint-plugin-promise 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 (53a2590237)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/jena-fuseki2/jena-fuseki-ui/eslint-plugin-promise-6.6.0
(579f5629c7)
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 | 223 ++++++++++++++++---------------
2 files changed, 115 insertions(+), 110 deletions(-)
