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

github-actions[bot] pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/datafusion-comet.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new c37a24e37 Publish built docs triggered by 
a2fd51baed1eecd6707512020b6fbbfea38d8019
c37a24e37 is described below

commit c37a24e37d2363a1b6ddb8ca4102e20ec8daebfa
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Thu May 7 17:19:32 2026 +0000

    Publish built docs triggered by a2fd51baed1eecd6707512020b6fbbfea38d8019
---
 _sources/contributor-guide/release_process.md.txt | 15 +++++++++++++++
 contributor-guide/release_process.html            | 14 ++++++++++++++
 searchindex.js                                    |  2 +-
 3 files changed, 30 insertions(+), 1 deletion(-)

diff --git a/_sources/contributor-guide/release_process.md.txt 
b/_sources/contributor-guide/release_process.md.txt
index 2a3c07adb..23d2b9110 100644
--- a/_sources/contributor-guide/release_process.md.txt
+++ b/_sources/contributor-guide/release_process.md.txt
@@ -158,6 +158,21 @@ commit into the release branch.
 
 ### Build the jars
 
+#### A note on workspace cleanliness
+
+The `common/pom.xml` resource configuration unconditionally bundles
+`native/target/{x86_64,aarch64}-apple-darwin/release/libcomet.dylib` into the
+`common` jar when those files exist on disk. Maven's `clean` removes
+`common/target` but does not touch Cargo's `native/target` directory, so a
+stale dylib left over from a prior local `make release` or `make release-linux`
+on the release manager's workstation can silently end up in a release jar
+(see [#2232](https://github.com/apache/datafusion-comet/issues/2232) for the
+incident in 0.9.1).
+
+The `build-release-comet.sh` script now runs `cargo clean` for you, but as a
+defensive measure, prefer running the release build from a fresh clone of the
+repository rather than your day-to-day working tree.
+
 #### Setup to do the build
 
 The build process requires Docker. Download the latest Docker Desktop from 
https://www.docker.com/products/docker-desktop/.
diff --git a/contributor-guide/release_process.html 
b/contributor-guide/release_process.html
index 7e3e69c49..11464b55d 100644
--- a/contributor-guide/release_process.html
+++ b/contributor-guide/release_process.html
@@ -590,6 +590,20 @@ commit into the release branch.</p>
 </section>
 <section id="build-the-jars">
 <h3>Build the jars<a class="headerlink" href="#build-the-jars" title="Link to 
this heading">#</a></h3>
+<section id="a-note-on-workspace-cleanliness">
+<h4>A note on workspace cleanliness<a class="headerlink" 
href="#a-note-on-workspace-cleanliness" title="Link to this heading">#</a></h4>
+<p>The <code class="docutils literal notranslate"><span 
class="pre">common/pom.xml</span></code> resource configuration unconditionally 
bundles
+<code class="docutils literal notranslate"><span 
class="pre">native/target/{x86_64,aarch64}-apple-darwin/release/libcomet.dylib</span></code>
 into the
+<code class="docutils literal notranslate"><span 
class="pre">common</span></code> jar when those files exist on disk. Maven’s 
<code class="docutils literal notranslate"><span 
class="pre">clean</span></code> removes
+<code class="docutils literal notranslate"><span 
class="pre">common/target</span></code> but does not touch Cargo’s <code 
class="docutils literal notranslate"><span 
class="pre">native/target</span></code> directory, so a
+stale dylib left over from a prior local <code class="docutils literal 
notranslate"><span class="pre">make</span> <span 
class="pre">release</span></code> or <code class="docutils literal 
notranslate"><span class="pre">make</span> <span 
class="pre">release-linux</span></code>
+on the release manager’s workstation can silently end up in a release jar
+(see <a class="reference external" 
href="https://github.com/apache/datafusion-comet/issues/2232";>#2232</a> for the
+incident in 0.9.1).</p>
+<p>The <code class="docutils literal notranslate"><span 
class="pre">build-release-comet.sh</span></code> script now runs <code 
class="docutils literal notranslate"><span class="pre">cargo</span> <span 
class="pre">clean</span></code> for you, but as a
+defensive measure, prefer running the release build from a fresh clone of the
+repository rather than your day-to-day working tree.</p>
+</section>
 <section id="setup-to-do-the-build">
 <h4>Setup to do the build<a class="headerlink" href="#setup-to-do-the-build" 
title="Link to this heading">#</a></h4>
 <p>The build process requires Docker. Download the latest Docker Desktop from 
https://www.docker.com/products/docker-desktop/.
diff --git a/searchindex.js b/searchindex.js
index 235c0cba6..d6436934d 100644
--- a/searchindex.js
+++ b/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"alltitles": {"1. Format Your Code": [[14, 
"format-your-code"]], "1. Install Comet": [[16, "install-comet"], [24, 
"install-comet"]], "1. Native Operators (nativeExecs map)": [[4, 
"native-operators-nativeexecs-map"]], "2. Build and Verify": [[14, 
"build-and-verify"]], "2. Clone Iceberg and Apply Diff": [[16, 
"clone-iceberg-and-apply-diff"]], "2. Clone Spark and Apply Diff": [[24, 
"clone-spark-and-apply-diff"]], "2. Sink Operators (sinks map)": [[4, 
"sink-operators-sinks-m [...]
\ No newline at end of file
+Search.setIndex({"alltitles": {"1. Format Your Code": [[14, 
"format-your-code"]], "1. Install Comet": [[16, "install-comet"], [24, 
"install-comet"]], "1. Native Operators (nativeExecs map)": [[4, 
"native-operators-nativeexecs-map"]], "2. Build and Verify": [[14, 
"build-and-verify"]], "2. Clone Iceberg and Apply Diff": [[16, 
"clone-iceberg-and-apply-diff"]], "2. Clone Spark and Apply Diff": [[24, 
"clone-spark-and-apply-diff"]], "2. Sink Operators (sinks map)": [[4, 
"sink-operators-sinks-m [...]
\ No newline at end of file


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

Reply via email to