[SPARK-58534][BUILD][4.x] Change version in branch-4.x to 4.4.0 - #57737
Closed
HeartSaVioR wants to merge 1 commit into
Closed
[SPARK-58534][BUILD][4.x] Change version in branch-4.x to 4.4.0#57737HeartSaVioR wants to merge 1 commit into
HeartSaVioR wants to merge 1 commit into
Conversation
Change version in `branch-4.x` to 4.4.0 (`4.3.0-SNAPSHOT` -> `4.4.0-SNAPSHOT`) now that `branch-4.3` has been cut for the 4.3.0 release. Mirrors SPARK-57443, which bumped `branch-4.x` to 4.3.0 after `branch-4.2` was cut: the project/parent version across all `pom.xml` files, plus `python/pyspark/version.py`, `R/pkg/DESCRIPTION`, `docs/_config.yml`, `resource-managers/kubernetes/integration-tests/README.md`, and a new `v44excludes` section in `project/MimaExcludes.scala`. Co-authored-by: Isaac
HeartSaVioR
commented
Aug 4, 2026
Contributor
Author
There was a problem hiding this comment.
This change also needs to go to master branch - I'll file a PR separately.
zhengruifeng
approved these changes
Aug 4, 2026
dongjoon-hyun
pushed a commit
that referenced
this pull request
Aug 4, 2026
### What changes were proposed in this pull request? Change version in `branch-4.x` to 4.4.0 (`4.3.0-SNAPSHOT` -> `4.4.0-SNAPSHOT`) now that `branch-4.3` has been cut for the 4.3.0 release. Mirrors SPARK-57443, which bumped `branch-4.x` to 4.3.0 after `branch-4.2` was cut: the project/parent version across all `pom.xml` files, plus `python/pyspark/version.py`, `R/pkg/DESCRIPTION`, `docs/_config.yml`, `resource-managers/kubernetes/integration-tests/README.md`, and a new `v44excludes` section in `project/MimaExcludes.scala`. ### Why are the changes needed? We just cut the branch for Apache Spark 4.3.0 and branch-4.x is expected to be reassigned to 4.4.0-SNAPSHOT. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? CI will test it out. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Opus 5 Closes #57737 from HeartSaVioR/bump-branch-4x-4.4.0. Authored-by: Jungtaek Lim <kabhwan.opensource@gmail.com> Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
Member
|
Merge Summary:
Posted by |
Contributor
Author
|
Thanks @dongjoon-hyun for reviewing and merging the PR! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Change version in
branch-4.xto 4.4.0 (4.3.0-SNAPSHOT->4.4.0-SNAPSHOT) now thatbranch-4.3has been cut for the 4.3.0 release.Mirrors SPARK-57443, which bumped
branch-4.xto 4.3.0 afterbranch-4.2was cut: the project/parent version across allpom.xmlfiles, pluspython/pyspark/version.py,R/pkg/DESCRIPTION,docs/_config.yml,resource-managers/kubernetes/integration-tests/README.md, and a newv44excludessection inproject/MimaExcludes.scala.Why are the changes needed?
We just cut the branch for Apache Spark 4.3.0 and branch-4.x is expected to be reassigned to 4.4.0-SNAPSHOT.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
CI will test it out.
Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Opus 5