[
https://issues.apache.org/jira/browse/SPARK-59099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyukjin Kwon resolved SPARK-59099.
----------------------------------
Fix Version/s: connect-rust-4.3.0
Resolution: Fixed
Issue resolved by pull request 83
[https://github.com/apache/spark-connect-rust/pull/83]
> 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
> Assignee: Hyukjin Kwon
> Priority: Major
> Labels: pull-request-available
> Fix For: connect-rust-4.3.0
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
