This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/npm_and_yarn/linting-23c806e90e
in repository https://gitbox.apache.org/repos/asf/fineract-backoffice-ui.git
omit bd323138 chore(deps-dev): bump the linting group across 1 directory
with 4 updates
add b32bb8df chore(deps-dev): bump the testing group across 1 directory
with 2 updates
add 4cace7bd Merge pull request #635 from
apache/dependabot/npm_and_yarn/testing-fed964820e
add d3743ca3 chore(deps-dev): bump the linting group across 1 directory
with 4 updates
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 (bd323138)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/linting-23c806e90e (d3743ca3)
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:
package-lock.json | 507 ++++++++++++++----------------------------------------
package.json | 4 +-
2 files changed, 133 insertions(+), 378 deletions(-)
