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

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


The following commit(s) were added to refs/heads/master by this push:
     new 270da6f9b7b3 [SPARK-46377][INFRA] Upgrade labeler action to v5
270da6f9b7b3 is described below

commit 270da6f9b7b331e455d1f0bd1309fb87bc8740ab
Author: panbingkun <[email protected]>
AuthorDate: Thu Dec 14 11:09:14 2023 +0800

    [SPARK-46377][INFRA] Upgrade labeler action to v5
    
    ### What changes were proposed in this pull request?
    The pr aims to upgrade `labeler action` from v4 to v5.
    
    ### Why are the changes needed?
    The full release notes: 
https://github.com/actions/labeler/releases/tag/v5.0.0
    Version 5 of this action updated the [runtime to Node.js 
20](https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-javascript-actions).
 All scripts are now run with Node.js 20 instead of Node.js 16 and are affected 
by any breaking changes between Node.js 16 and 20.
    
    ### Does this PR introduce _any_ user-facing change?
    No.
    
    ### How was this patch tested?
    - Pass GA.
    - Manually continuous observation.
    
    ### Was this patch authored or co-authored using generative AI tooling?
    No.
    
    Closes #44309 from panbingkun/SPARK-46377.
    
    Authored-by: panbingkun <[email protected]>
    Signed-off-by: Kent Yao <[email protected]>
---
 .github/workflows/labeler.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/labeler.yml b/.github/workflows/labeler.yml
index b55d28e5a640..ccfdeb1653b9 100644
--- a/.github/workflows/labeler.yml
+++ b/.github/workflows/labeler.yml
@@ -34,7 +34,7 @@ jobs:
       contents: read
       pull-requests: write
     steps:
-    - uses: actions/labeler@v4
+    - uses: actions/labeler@v5
       with:
         repo-token: "${{ secrets.GITHUB_TOKEN }}"
         sync-labels: true


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

Reply via email to