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

yangjie01 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 f7309f286f98 [SPARK-53709][BUILD] Upgrade Junit to 5.13.4
f7309f286f98 is described below

commit f7309f286f98774ea0f92f070ecc233fcfe27a0f
Author: YangJie <[email protected]>
AuthorDate: Thu Sep 25 15:07:20 2025 +0800

    [SPARK-53709][BUILD] Upgrade Junit to 5.13.4
    
    ### What changes were proposed in this pull request?
    This PR aims to upgrade `Junit` from 5.13.1 to 5.13.4.
    
    ### Why are the changes needed?
    The full release notes as follows:
    
    **sbt-jupiter-interface**
    
    - https://github.com/sbt/sbt-jupiter-interface/releases/tag/v0.15.1
    
    **Junit5**
    
    - https://docs.junit.org/5.13.4/release-notes/#release-notes-5.13.4
    - https://docs.junit.org/5.13.4/release-notes/#release-notes-5.13.3
    - https://docs.junit.org/5.13.4/release-notes/#release-notes-5.13.2
    
    ### Does this PR introduce _any_ user-facing change?
    No
    
    ### How was this patch tested?
    Pass Github Actions
    
    ### Was this patch authored or co-authored using generative AI tooling?
    No
    
    Closes #52447 from LuciferYang/junit-5.13.4.
    
    Lead-authored-by: YangJie <[email protected]>
    Co-authored-by: yangjie01 <[email protected]>
    Signed-off-by: yangjie01 <[email protected]>
---
 pom.xml                  | 6 +++---
 project/SparkBuild.scala | 2 +-
 project/plugins.sbt      | 2 +-
 3 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/pom.xml b/pom.xml
index 864d113b3cd7..1438271d2f77 100644
--- a/pom.xml
+++ b/pom.xml
@@ -220,13 +220,13 @@
     <netty.version>4.1.127.Final</netty.version>
     <netty-tcnative.version>2.0.73.Final</netty-tcnative.version>
     <icu4j.version>77.1</icu4j.version>
-    <junit-jupiter.version>5.13.1</junit-jupiter.version>
-    <junit-platform.version>1.13.1</junit-platform.version>
+    <junit-jupiter.version>5.13.4</junit-jupiter.version>
+    <junit-platform.version>1.13.4</junit-platform.version>
     <!--
       SPARK-50299: When updating `sbt-jupiter-interface.version`,
       also need to update the version in `SparkBuild.scala` and `plugins.sbt`.
     -->
-    <sbt-jupiter-interface.version>0.15.0</sbt-jupiter-interface.version>
+    <sbt-jupiter-interface.version>0.15.1</sbt-jupiter-interface.version>
     <!--
     If you are changing Arrow version specification, please check
     ./python/pyspark/sql/pandas/utils.py, ./python/packaging/classic/setup.py,
diff --git a/project/SparkBuild.scala b/project/SparkBuild.scala
index f26879a90edf..09459671b3cc 100644
--- a/project/SparkBuild.scala
+++ b/project/SparkBuild.scala
@@ -1755,7 +1755,7 @@ object TestSettings {
     (Test / testOptions) += Tests.Argument(TestFrameworks.ScalaTest, "-W", 
"120", "300"),
     (Test / testOptions) += Tests.Argument(TestFrameworks.JUnit, "-v", "-a"),
     // Enable Junit testing.
-    libraryDependencies += "com.github.sbt.junit" % "jupiter-interface" % 
"0.15.0" % "test",
+    libraryDependencies += "com.github.sbt.junit" % "jupiter-interface" % 
"0.15.1" % "test",
     // `parallelExecutionInTest` controls whether test suites belonging to the 
same SBT project
     // can run in parallel with one another. It does NOT control whether tests 
execute in parallel
     // within the same JVM (which is controlled by `testForkedParallel`) or 
whether test cases
diff --git a/project/plugins.sbt b/project/plugins.sbt
index f92705373e20..9cfc324a751d 100644
--- a/project/plugins.sbt
+++ b/project/plugins.sbt
@@ -41,6 +41,6 @@ addSbtPlugin("com.simplytyped" % "sbt-antlr4" % "0.8.3")
 
 addSbtPlugin("com.github.sbt" % "sbt-pom-reader" % "2.4.0")
 
-addSbtPlugin("com.github.sbt.junit" % "sbt-jupiter-interface" % "0.15.0")
+addSbtPlugin("com.github.sbt.junit" % "sbt-jupiter-interface" % "0.15.1")
 
 addSbtPlugin("com.thesamet" % "sbt-protoc" % "1.0.7")


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

Reply via email to