HyukjinKwon opened a new pull request, #83:
URL: https://github.com/apache/spark-connect-rust/pull/83

   ### What changes were proposed in this pull request?
   
   `branch-4.2` has been cut as the 4.2.x maintenance line. This bumps the 
**master** development version to `4.3.0` so master and `branch-4.2` diverge, 
and future 4.2.x fixes are backported rather than landing on master.
   
   It 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) — `4.2.0` → `4.3.0`
   - `pyproject.toml` (package version) — `4.2.0` → `4.3.0`
   - `crates/spark-connect-core/Cargo.toml`, `crates/spark-connect/Cargo.toml` 
(internal path-dep version pins)
   - `Cargo.lock` (regenerated)
   
   The **vendored Apache Spark version is unchanged**: we still vendor Spark 
4.2.0 (the drift check's `SPARK_TAG` and the vendored proto/Python remain 
`v4.2.0`) until master is re-vendored to a newer Spark.
   
   ### Why are the changes needed?
   
   Standard post-branch-cut step: master must carry the next development 
version so releases on `branch-4.2` and ongoing development on master don't 
collide.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No. Development-version bump only; no released artifact changes.
   
   ### How was this patch tested?
   
   `cargo build -p pyspark-rs` succeeds with the bumped version pins; the 
release workflow's `validate-version` invariants (Cargo/pyproject agree, 
internal path-dep pins match the workspace version) hold at `4.3.0`.
   
   This pull request and its description were written by Isaac.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to