This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch 
dependabot/npm_and_yarn/src/flagd-ui/npm-production-dependencies-50eaf87afe
in repository https://gitbox.apache.org/repos/asf/doris-opentelemetry-demo.git


 discard 7a26318  build(deps): bump the npm-production-dependencies group 
across 3 directories with 38 updates
     add e6042b7  fix:dashboard render
     add 0df51fb  Merge pull request #184 from yang1666204/fix_dashboard_render
     add 0f13fd1  build(deps): bump the npm-production-dependencies group 
across 3 directories with 38 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   (7a26318)
            \
             N -- N -- N   
refs/heads/dependabot/npm_and_yarn/src/flagd-ui/npm-production-dependencies-50eaf87afe
 (0f13fd1)

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:
 src/flagd-ui/package-lock.json            |  380 +++----
 src/flagd-ui/package.json                 |    8 +-
 src/frontend/package-lock.json            | 1578 ++++++++++++++++-------------
 src/frontend/package.json                 |   56 +-
 src/grafana/plugins/doris-app/plugin.json |    2 +-
 src/payment/package-lock.json             | 1026 ++++++++++---------
 src/payment/package.json                  |   30 +-
 7 files changed, 1653 insertions(+), 1427 deletions(-)


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to