This is an automated email from the ASF dual-hosted git repository.
kinow pushed a change to branch jena5-upgrade-ui-deps
in repository https://gitbox.apache.org/repos/asf/jena.git
discard 8c5e55dab5 Used ncu to upgrade deps, tested manually and unit tests,
e2e tests appear to be working too, but the automation is borked
new 1e00512f47 [GH-2054] Upgrade UI dependencies to latest.
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 (8c5e55dab5)
\
N -- N -- N refs/heads/jena5-upgrade-ui-deps (1e00512f47)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
jena-fuseki2/jena-fuseki-ui/yarn.lock | 349 +++++++++++++++++++++++++++-------
1 file changed, 281 insertions(+), 68 deletions(-)
