You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (Jira)" <ji...@apache.org> on 2026/08/29 06:37:00 UTC

[jira] [Created] (SPARK-59099) Bump master development version to 4.3.0 after cutting branch-4.2

Hyukjin Kwon created SPARK-59099:
------------------------------------

             Summary: Bump master development version to 4.3.0 after cutting branch-4.2
                 Key: SPARK-59099
                 URL: https://issues.apache.org/jira/browse/SPARK-59099
             Project: Spark
          Issue Type: Improvement
          Components: Connect
    Affects Versions: connect-rust-4.2.0
            Reporter: Hyukjin Kwon


Following the cut of branch-4.2 (the 4.2.x maintenance line), bump the master development version to 4.3.0 so master and branch-4.2 diverge and 4.2.x work is backported rather than landing on master.

This touches only the *client* crate/package version and the internal path-dependency version pins that the release workflow's validate-version step requires to agree:
- Cargo.toml (workspace version)
- pyproject.toml (package version)
- crates/spark-connect-core/Cargo.toml, crates/spark-connect/Cargo.toml (internal path-dep pins)
- Cargo.lock (regenerated)

The vendored Apache Spark version is unchanged: we still vendor Spark 4.2.0 (drift-check SPARK_TAG and the vendored proto/Python remain v4.2.0) until master is re-vendored to a newer Spark.

Note: fixVersion is set to connect-rust-4.2.0 because a connect-rust-4.3.0 version does not yet exist in JIRA.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org