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

srowen 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 93d169db319 [SPARK-42245][BUILD] Upgrade scalafmt from 3.6.1 to 3.7.1
93d169db319 is described below

commit 93d169db31991c354cb46c3bacc0de4f0517d819
Author: panbingkun <pbk1...@gmail.com>
AuthorDate: Tue Jan 31 09:32:11 2023 -0600

    [SPARK-42245][BUILD] Upgrade scalafmt from 3.6.1 to 3.7.1
    
    ### What changes were proposed in this pull request?
    The pr aims to upgrade scalafmt from 3.6.1 to 3.7.1
    
    ### Why are the changes needed?
    A. Release note:
    > https://github.com/scalameta/scalafmt/releases
    
    B. V3.6.1 VS V3.7.1
    > https://github.com/scalameta/scalafmt/compare/v3.6.1...v3.7.1
    
    C. Bring bug fix & some improvement:
    <img width="571" alt="image" 
src="https://user-images.githubusercontent.com/15246973/215639186-47ad2abc-5827-4b0b-a401-10737bd05743.png";>
    <img width="641" alt="image" 
src="https://user-images.githubusercontent.com/15246973/215639316-0df69d85-cb6b-40f8-acbf-d792193d1ba1.png";>
    
    ### Does this PR introduce _any_ user-facing change?
    No.
    
    ### How was this patch tested?
    Manually run: sh ./dev/scalafmt
    Pass GA.
    
    Closes #39816 from panbingkun/upgrade_scalafmt_3_7_1.
    
    Authored-by: panbingkun <pbk1...@gmail.com>
    Signed-off-by: Sean Owen <sro...@gmail.com>
---
 dev/.scalafmt.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev/.scalafmt.conf b/dev/.scalafmt.conf
index e06ea5bbfd2..786259ea4db 100644
--- a/dev/.scalafmt.conf
+++ b/dev/.scalafmt.conf
@@ -32,4 +32,4 @@ fileOverride {
     runner.dialect = scala213
   }
 }
-version = 3.6.1
+version = 3.7.1


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@spark.apache.org
For additional commands, e-mail: commits-h...@spark.apache.org

Reply via email to