(zeppelin) branch master updated: [ZEPPELIN-6110][FOLLOWUP] Regenerate `package-lock.json`

[chengpan]

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

chengpan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/zeppelin.git


The following commit(s) were added to refs/heads/master by this push:
     new 70013d725c [ZEPPELIN-6110][FOLLOWUP] Regenerate `package-lock.json`
70013d725c is described below

commit 70013d725cdb9187f0e1b3e240680d464e318db7
Author: Cheng Pan <cheng...@apache.org>
AuthorDate: Sat Oct 5 20:57:52 2024 +0800

    [ZEPPELIN-6110][FOLLOWUP] Regenerate `package-lock.json`
    
    ### What is this PR for?
    
    `package-lock.json` content changed after performing `npm install`.
    
    ### What type of PR is it?
    
    Improvement
    
    ### Todos
    
    ### What is the Jira issue?
    
    ZEPPELIN-6110
    
    ### How should this be tested?
    
    Pass CI.
    
    ### Screenshots (if appropriate)
    
    ### Questions:
    * Does the license files need to update? No.
    * Is there breaking changes for older versions? No.
    * Does this needs documentation? No.
    
    
    Closes #4860 from pan3793/ZEPPELIN-6110-followup.
    
    Signed-off-by: Cheng Pan <cheng...@apache.org>
---
 zeppelin-web-angular/package-lock.json | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/zeppelin-web-angular/package-lock.json 
b/zeppelin-web-angular/package-lock.json
index 3f82465b82..acfe98974a 100644
--- a/zeppelin-web-angular/package-lock.json
+++ b/zeppelin-web-angular/package-lock.json
@@ -74,6 +74,9 @@
         "tsickle": "0.37.0",
         "tslint": "~5.15.0",
         "typescript": "3.5.3"
+      },
+      "engines": {
+        "node": "<17.0.0"
       }
     },
     "node_modules/@angular-devkit/architect": {