You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@iceberg.apache.org by gi...@apache.org on 2026/09/11 22:35:00 UTC
(iceberg-rust) branch gh-pages updated: deploy: cb912c91066f4fc9bca8b5cdebc40e79aef38d9f
This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a commit to branch gh-pages
in repository https://gitbox.apache.org/repos/asf/iceberg-rust.git
The following commit(s) were added to refs/heads/gh-pages by this push:
new c4e55dd75 deploy: cb912c91066f4fc9bca8b5cdebc40e79aef38d9f
c4e55dd75 is described below
commit c4e55dd753929ca614b5db79c681dc00a76e407a
Author: CTTY <CT...@users.noreply.github.com>
AuthorDate: Fri Sep 11 22:34:54 2026 +0000
deploy: cb912c91066f4fc9bca8b5cdebc40e79aef38d9f
---
api/search.index/path/33779bc049.js | 1 +
api/search.index/path/d6ecb988e9.js | 1 -
api/search.index/root.js | 2 +-
print.html | 98 ++++++++++++++++++++++++++-----------
release.html | 98 ++++++++++++++++++++++++++-----------
searchindex.js | 2 +-
searchindex.json | 2 +-
7 files changed, 144 insertions(+), 60 deletions(-)
diff --git a/api/search.index/path/33779bc049.js b/api/search.index/path/33779bc049.js
new file mode 100644
index 000000000..c234e4a4a
--- /dev/null
+++ b/api/search.index/path/33779bc049.js
@@ -0,0 +1 @@
+rd_("g[17,\"\"]000f[1,\"\"]0Aa[10,\"bnum::cast\"]Bn[15,\"iceberg_storage_opendal::OpenDalStorage\"]Eg[5,\"tower_http::follow_redirect::policy::or\",\"tower_http::follow_redirect::policy::or\"]1Ce[15,\"iceberg_storage_opendal::OpenDalStorageFactory\"]4Bb[2,\"iceberg::io::storage::config\"]m[2,\"iceberg\"]Ai[2,\"iceberg::encryption\"]2Am[2,\"iceberg_storage_opendal\"]8Ei[5,\"tower_http::follow_redirect::policy::and\",\"tower_http::follow_redirect::policy::and\"]A`[10,\"core::any\"]Ao[5,\"a [...]
\ No newline at end of file
diff --git a/api/search.index/path/d6ecb988e9.js b/api/search.index/path/d6ecb988e9.js
deleted file mode 100644
index f548459d5..000000000
--- a/api/search.index/path/d6ecb988e9.js
+++ /dev/null
@@ -1 +0,0 @@
-rd_("g[17,\"\"]000f[1,\"\"]0Aa[10,\"bnum::cast\"]Bn[15,\"iceberg_storage_opendal::OpenDalStorage\"]Eg[5,\"tower_http::follow_redirect::policy::or\",\"tower_http::follow_redirect::policy::or\"]1Ce[15,\"iceberg_storage_opendal::OpenDalStorageFactory\"]4Bb[2,\"iceberg::io::storage::config\"]m[2,\"iceberg\"]Ai[2,\"iceberg::encryption\"]2Am[2,\"iceberg_storage_opendal\"]8Ei[5,\"tower_http::follow_redirect::policy::and\",\"tower_http::follow_redirect::policy::and\"]A`[10,\"core::any\"]Ao[5,\"a [...]
\ No newline at end of file
diff --git a/api/search.index/root.js b/api/search.index/root.js
index 019818b1d..ce2f3b89b 100644
--- a/api/search.index/root.js
+++ b/api/search.index/root.js
@@ -1 +1 @@
-rr_('{"normalizedName":{"I":"VYLAAAAUexSTAVsH1wxzD5oPJQHAAAAwrAObBAEFNP8EdQ8lAcAAABB1DzZ1F8YiRQHAAAAS2QxypQGsA5sEAQV1/MBEAgAAQVsH1wxzD5oPEP8EEXQPHwAgACEAlAFVESUgZCIVAcAAACFMEe8cbqYBBQLAAAATEiAQ7hxhcwEBAcUAABxSZDswAAABAAD0AAMACwUAACIFAACXCfIABQLDAACnLiKiYyFkc0UBwgAAFR0bY44KjwqQCsoKFQHAAAAS2QxypQEUAcJ0ZAAAFmVmYXVsdL8cZCUFdhsAAf4IThwAFxem8V7EAAAgf3MA0kAbAAC+FQHRAAAW0CJkpiIVAdYAABbeImTPIjHAAAAwEfAe8R7zgQJmcGUBwwAAFtgiZNQhYSKVIpYiuyK/IkUBwwAAFtIiZNgapR5FIq4iIwACxAAAITRhbvQrHAAApAFWBDcA+4YJAtA [...]
\ No newline at end of file
+rr_('{"normalizedName":{"I":"VYLAAAAUexSTAVsH1wxzD5oPJQHAAAAwrAObBAEFNP8EdQ8lAcAAABB1DzZ1F8YiRQHAAAAS2QxypQGsA5sEAQV1/MBEAgAAQVsH1wxzD5oPEP8EEXQPHwAgACEAlAFVESUgZCIVAcAAACFMEe8cbqYBBQLAAAATEiAQ7hxhcwEBAcUAABxSZDswAAABAAD0AAMACwUAACIFAACXCfIABQLDAACnLiKiYyFkc0UBwgAAFR0bY44KjwqQCsoKFQHAAAAS2QxypQEUAcJ0ZAAAFmVmYXVsdL8cZCUFdhsAAf4IThwAFxem8V7EAAAgf3MA0kAbAAC+FQHRAAAW0CJkpiIVAdYAABbeImTPIjHAAAAwEfAe8R7zgQJmcGUBwwAAFtgiZNQhYSKVIpYiuyK/IkUBwwAAFtIiZNgapR5FIq4iIwACxAAAITRhbvQrHAAApAFWBDcA+4YJAtA [...]
\ No newline at end of file
diff --git a/print.html b/print.html
index e1fb44d76..aa9ad7d20 100644
--- a/print.html
+++ b/print.html
@@ -1472,9 +1472,8 @@ Review the output and then manually publish the release tag.</p>
<p>The creation of the final release tag triggers the publish workflow for crates.
Python packages are manually triggered later.
Please verify that the triggered workflows for the crates succeeded.</p>
-<p>Note, this workflow for crates is expected to fail if new crates are being published for the first time.
-In this instance, a committer must manually publish the crate in order to continue.
-See <a href="release.html#publishing-a-crate-for-the-first-time">publishing a crate for the first time</a> for what steps to take.
+<p>New crates are reserved on crates.io when they are added, so the workflow should not fail on a new crate.
+If it does, see <a href="release.html#if-the-publish-workflow-fails-on-a-missing-crate">if the Publish workflow fails on a missing crate</a>.
Once all the crates are published, Python publishing should start.</p>
<p>Python publishing is performed by a GitHub workflow, however the trigger is manual.
Trigger this now using the following GitHub CLI command, or the equivalent on the GitHub website.
@@ -1533,31 +1532,74 @@ On behalf of Apache Iceberg Community
It does not need to be published immediately for the release to be considered complete,
however it is in the community's best interest to publish it soon after.</p>
<h2 id="appendix"><a class="header" href="#appendix">Appendix</a></h2>
-<h3 id="publishing-a-crate-for-the-first-time"><a class="header" href="#publishing-a-crate-for-the-first-time">Publishing a crate for the first time</a></h3>
-<p>Publishing the Iceberg crates is automated using GitHub Actions,
-which authenticates with crates.io using trusted publishing.</p>
-<p>Trusted publishing must first be configured for each crate.
-If the crate has never been published, crates.io rejects attempts to publish.</p>
-<p>When a release workflow fails due to the presence of a new crate, a committer must perform steps enumerated below.
-Once complete, future versions can be published automatically using GitHub Actions.</p>
-<h4 id="initial-crate-publish"><a class="header" href="#initial-crate-publish">Initial crate publish</a></h4>
-<p>Manually publish the crate using the following command.
-You <strong>must</strong> have the source code checked out matching the pushed Git tag for the release.</p>
-<pre><code class="language-shell">cargo publish --package <package-name>
-</code></pre>
-<h4 id="configure-crate-permissions"><a class="header" href="#configure-crate-permissions">Configure crate permissions</a></h4>
-<p>After publishing succeeds, the crate must be configured to allow other committers to publish.</p>
-<p>Add the GitHub team that Apache Iceberg committers are a member of.</p>
-<pre><code class="language-shell">cargo owner --add github:<github-team-org>:<github-team-name>
-</code></pre>
-<p>Additionally, add two PMC members (excluding yourself) as owners of the crate.
-A GitHub team cannot manage permissions for the crate, so it is important that individuals have ownership to continue being able to manage the crate should a PMC member become inactive.
-See the <a href="https://doc.rust-lang.org/cargo/reference/publishing.html#cargo-owner">Cargo documentation for <code>cargo owner</code></a> for reference.</p>
-<pre><code class="language-shell">cargo owner --add <github-handle>
-</code></pre>
-<h4 id="configure-trusted-publishing"><a class="header" href="#configure-trusted-publishing">Configure trusted publishing</a></h4>
-<p>Review the <a href="https://crates.io/docs/trusted-publishing">crates.io trusted publishing documentation</a> for the latest instructions on how to configure it.
-You should also review another already-existing crate for reference.</p>
+<h3 id="adding-a-new-crate"><a class="header" href="#adding-a-new-crate">Adding a new crate</a></h3>
+<p>Every publishable crate must exist on crates.io before the pull request that adds it is merged.
+CI enforces this with a check that fails for any publishable crate missing from crates.io.</p>
+<p>The release workflow publishes crates with <a href="https://crates.io/docs/trusted-publishing">trusted publishing</a>, which cannot create a crate.
+crates.io requires the first version of a crate to be published manually with an API token (<a href="https://blog.rust-lang.org/2025/07/11/crates-io-development-update-2025-07/">announcement</a>).
+Publishing the crate by hand after the release workflow fails does not work either: the workflow runs <code>cargo publish --workspace</code>, which refuses to run if any crate already exists at the release version.</p>
+<p>A committer therefore reserves the crate when it is added, in three steps: publish a placeholder version, configure owners, and configure trusted publishing.</p>
+<h4 id="prerequisites"><a class="header" href="#prerequisites">Prerequisites</a></h4>
+<p>Any crates.io account can publish an unclaimed name, and the first publisher becomes the crate's only owner.
+Reserve the crate promptly once the pull request is open, and have a committer do it, since the reserver must hand ownership to the project.</p>
+<p>The committer needs:</p>
+<ul>
+<li>A crates.io account linked to their GitHub account.</li>
+<li>Membership in the <code>apache/iceberg-private</code> GitHub team, with the <code>read:org</code> permission granted to crates.io, in order to add that team as an owner.</li>
+<li>A crates.io API token with the <code>publish-new</code> and <code>change-owners</code> scopes, used with <code>cargo login</code>.
+Existing tokens usually lack <code>publish-new</code>; create one at <a href="https://crates.io/settings/tokens">crates.io/settings/tokens</a>.</li>
+</ul>
+<p>Committers who already own the existing Iceberg crates meet the first two.
+List them with <code>cargo owner --list iceberg</code>.</p>
+<h4 id="step-1-reserve-the-crate-name"><a class="header" href="#step-1-reserve-the-crate-name">Step 1: Reserve the crate name</a></h4>
+<p>Publish an empty placeholder crate as version <code>0.0.0</code>, so it never collides with a real release.
+The placeholder is created outside the repository; overriding the version inside the workspace does not work because other workspace crates depend on the new crate at the workspace version.</p>
+<pre><code class="language-shell">mkdir -p /tmp/<package-name>/src
+cd /tmp/<package-name>
+touch src/lib.rs
+cat > Cargo.toml <<'EOF'
+[package]
+name = "<package-name>"
+version = "0.0.0"
+edition = "2024"
+license = "Apache-2.0"
+description = "Placeholder that reserves the crate name for Apache Iceberg Rust. See the repository for the real crate."
+repository = "https://github.com/apache/iceberg-rust"
+EOF
+cargo publish --dry-run
+cargo publish
+</code></pre>
+<p>A <code>403 Forbidden: authentication failed</code> error means the token lacks the <code>publish-new</code> scope.</p>
+<h4 id="step-2-configure-crate-owners"><a class="header" href="#step-2-configure-crate-owners">Step 2: Configure crate owners</a></h4>
+<p>Add the GitHub team that owns the existing Iceberg crates.</p>
+<pre><code class="language-shell">cargo owner --add github:apache:iceberg-private <package-name>
+</code></pre>
+<p>Then add two PMC members other than yourself as individual owners.</p>
+<pre><code class="language-shell">cargo owner --add <github-handle> <package-name>
+</code></pre>
+<p>This sends an invitation; ask each invitee to accept it on crates.io.</p>
+<p>Individual owners are required because a team owner can publish and yank versions but cannot add or remove owners.
+Without them, the crate could become unmanageable if a PMC member becomes inactive.
+See the <a href="https://doc.rust-lang.org/cargo/reference/publishing.html#cargo-owner">Cargo documentation for <code>cargo owner</code></a>.</p>
+<h4 id="step-3-configure-trusted-publishing"><a class="header" href="#step-3-configure-trusted-publishing">Step 3: Configure trusted publishing</a></h4>
+<p>As a crate owner, open the crate's settings on the crates.io website and add a trusted publisher, following the <a href="https://crates.io/docs/trusted-publishing">crates.io trusted publishing documentation</a>.
+Use an existing Iceberg crate as the reference:</p>
+<ul>
+<li>Repository: <code>apache/iceberg-rust</code></li>
+<li>Workflow: <code>publish.yml</code></li>
+<li>Environment: <code>publish</code></li>
+</ul>
+<p>Then re-run CI on the pull request.
+The next release publishes the crate's first real version along with the rest of the workspace.</p>
+<h4 id="if-the-publish-workflow-fails-on-a-missing-crate"><a class="header" href="#if-the-publish-workflow-fails-on-a-missing-crate">If the Publish workflow fails on a missing crate</a></h4>
+<p>Reserve the crate as above, using the <code>0.0.0</code> placeholder and never the release version.</p>
+<p>Then check the failed run's log for <code>Uploaded</code> lines to see which crates were already published, since cargo uploads crates one at a time in dependency order.</p>
+<ul>
+<li>If nothing was uploaded, re-run the failed workflow run from the GitHub Actions UI. Re-running keeps the original tag as the workflow ref.</li>
+<li>If some crates were uploaded, publish the rest from a clean checkout of the release tag, excluding each crate that was already published:</li>
+</ul>
+<pre><code class="language-shell">cargo publish --workspace --all-features --exclude <published-crate> --exclude <published-crate>
+</code></pre>
<div style="break-before: page; page-break-before: always;"></div><!--
~ Licensed to the Apache Software Foundation (ASF) under one
~ or more contributor license agreements. See the NOTICE file
diff --git a/release.html b/release.html
index 9d1b4a718..983193def 100644
--- a/release.html
+++ b/release.html
@@ -562,9 +562,8 @@ Review the output and then manually publish the release tag.</p>
<p>The creation of the final release tag triggers the publish workflow for crates.
Python packages are manually triggered later.
Please verify that the triggered workflows for the crates succeeded.</p>
-<p>Note, this workflow for crates is expected to fail if new crates are being published for the first time.
-In this instance, a committer must manually publish the crate in order to continue.
-See <a href="#publishing-a-crate-for-the-first-time">publishing a crate for the first time</a> for what steps to take.
+<p>New crates are reserved on crates.io when they are added, so the workflow should not fail on a new crate.
+If it does, see <a href="#if-the-publish-workflow-fails-on-a-missing-crate">if the Publish workflow fails on a missing crate</a>.
Once all the crates are published, Python publishing should start.</p>
<p>Python publishing is performed by a GitHub workflow, however the trigger is manual.
Trigger this now using the following GitHub CLI command, or the equivalent on the GitHub website.
@@ -623,31 +622,74 @@ On behalf of Apache Iceberg Community
It does not need to be published immediately for the release to be considered complete,
however it is in the community's best interest to publish it soon after.</p>
<h2 id="appendix"><a class="header" href="#appendix">Appendix</a></h2>
-<h3 id="publishing-a-crate-for-the-first-time"><a class="header" href="#publishing-a-crate-for-the-first-time">Publishing a crate for the first time</a></h3>
-<p>Publishing the Iceberg crates is automated using GitHub Actions,
-which authenticates with crates.io using trusted publishing.</p>
-<p>Trusted publishing must first be configured for each crate.
-If the crate has never been published, crates.io rejects attempts to publish.</p>
-<p>When a release workflow fails due to the presence of a new crate, a committer must perform steps enumerated below.
-Once complete, future versions can be published automatically using GitHub Actions.</p>
-<h4 id="initial-crate-publish"><a class="header" href="#initial-crate-publish">Initial crate publish</a></h4>
-<p>Manually publish the crate using the following command.
-You <strong>must</strong> have the source code checked out matching the pushed Git tag for the release.</p>
-<pre><code class="language-shell">cargo publish --package <package-name>
-</code></pre>
-<h4 id="configure-crate-permissions"><a class="header" href="#configure-crate-permissions">Configure crate permissions</a></h4>
-<p>After publishing succeeds, the crate must be configured to allow other committers to publish.</p>
-<p>Add the GitHub team that Apache Iceberg committers are a member of.</p>
-<pre><code class="language-shell">cargo owner --add github:<github-team-org>:<github-team-name>
-</code></pre>
-<p>Additionally, add two PMC members (excluding yourself) as owners of the crate.
-A GitHub team cannot manage permissions for the crate, so it is important that individuals have ownership to continue being able to manage the crate should a PMC member become inactive.
-See the <a href="https://doc.rust-lang.org/cargo/reference/publishing.html#cargo-owner">Cargo documentation for <code>cargo owner</code></a> for reference.</p>
-<pre><code class="language-shell">cargo owner --add <github-handle>
-</code></pre>
-<h4 id="configure-trusted-publishing"><a class="header" href="#configure-trusted-publishing">Configure trusted publishing</a></h4>
-<p>Review the <a href="https://crates.io/docs/trusted-publishing">crates.io trusted publishing documentation</a> for the latest instructions on how to configure it.
-You should also review another already-existing crate for reference.</p>
+<h3 id="adding-a-new-crate"><a class="header" href="#adding-a-new-crate">Adding a new crate</a></h3>
+<p>Every publishable crate must exist on crates.io before the pull request that adds it is merged.
+CI enforces this with a check that fails for any publishable crate missing from crates.io.</p>
+<p>The release workflow publishes crates with <a href="https://crates.io/docs/trusted-publishing">trusted publishing</a>, which cannot create a crate.
+crates.io requires the first version of a crate to be published manually with an API token (<a href="https://blog.rust-lang.org/2025/07/11/crates-io-development-update-2025-07/">announcement</a>).
+Publishing the crate by hand after the release workflow fails does not work either: the workflow runs <code>cargo publish --workspace</code>, which refuses to run if any crate already exists at the release version.</p>
+<p>A committer therefore reserves the crate when it is added, in three steps: publish a placeholder version, configure owners, and configure trusted publishing.</p>
+<h4 id="prerequisites"><a class="header" href="#prerequisites">Prerequisites</a></h4>
+<p>Any crates.io account can publish an unclaimed name, and the first publisher becomes the crate's only owner.
+Reserve the crate promptly once the pull request is open, and have a committer do it, since the reserver must hand ownership to the project.</p>
+<p>The committer needs:</p>
+<ul>
+<li>A crates.io account linked to their GitHub account.</li>
+<li>Membership in the <code>apache/iceberg-private</code> GitHub team, with the <code>read:org</code> permission granted to crates.io, in order to add that team as an owner.</li>
+<li>A crates.io API token with the <code>publish-new</code> and <code>change-owners</code> scopes, used with <code>cargo login</code>.
+Existing tokens usually lack <code>publish-new</code>; create one at <a href="https://crates.io/settings/tokens">crates.io/settings/tokens</a>.</li>
+</ul>
+<p>Committers who already own the existing Iceberg crates meet the first two.
+List them with <code>cargo owner --list iceberg</code>.</p>
+<h4 id="step-1-reserve-the-crate-name"><a class="header" href="#step-1-reserve-the-crate-name">Step 1: Reserve the crate name</a></h4>
+<p>Publish an empty placeholder crate as version <code>0.0.0</code>, so it never collides with a real release.
+The placeholder is created outside the repository; overriding the version inside the workspace does not work because other workspace crates depend on the new crate at the workspace version.</p>
+<pre><code class="language-shell">mkdir -p /tmp/<package-name>/src
+cd /tmp/<package-name>
+touch src/lib.rs
+cat > Cargo.toml <<'EOF'
+[package]
+name = "<package-name>"
+version = "0.0.0"
+edition = "2024"
+license = "Apache-2.0"
+description = "Placeholder that reserves the crate name for Apache Iceberg Rust. See the repository for the real crate."
+repository = "https://github.com/apache/iceberg-rust"
+EOF
+cargo publish --dry-run
+cargo publish
+</code></pre>
+<p>A <code>403 Forbidden: authentication failed</code> error means the token lacks the <code>publish-new</code> scope.</p>
+<h4 id="step-2-configure-crate-owners"><a class="header" href="#step-2-configure-crate-owners">Step 2: Configure crate owners</a></h4>
+<p>Add the GitHub team that owns the existing Iceberg crates.</p>
+<pre><code class="language-shell">cargo owner --add github:apache:iceberg-private <package-name>
+</code></pre>
+<p>Then add two PMC members other than yourself as individual owners.</p>
+<pre><code class="language-shell">cargo owner --add <github-handle> <package-name>
+</code></pre>
+<p>This sends an invitation; ask each invitee to accept it on crates.io.</p>
+<p>Individual owners are required because a team owner can publish and yank versions but cannot add or remove owners.
+Without them, the crate could become unmanageable if a PMC member becomes inactive.
+See the <a href="https://doc.rust-lang.org/cargo/reference/publishing.html#cargo-owner">Cargo documentation for <code>cargo owner</code></a>.</p>
+<h4 id="step-3-configure-trusted-publishing"><a class="header" href="#step-3-configure-trusted-publishing">Step 3: Configure trusted publishing</a></h4>
+<p>As a crate owner, open the crate's settings on the crates.io website and add a trusted publisher, following the <a href="https://crates.io/docs/trusted-publishing">crates.io trusted publishing documentation</a>.
+Use an existing Iceberg crate as the reference:</p>
+<ul>
+<li>Repository: <code>apache/iceberg-rust</code></li>
+<li>Workflow: <code>publish.yml</code></li>
+<li>Environment: <code>publish</code></li>
+</ul>
+<p>Then re-run CI on the pull request.
+The next release publishes the crate's first real version along with the rest of the workspace.</p>
+<h4 id="if-the-publish-workflow-fails-on-a-missing-crate"><a class="header" href="#if-the-publish-workflow-fails-on-a-missing-crate">If the Publish workflow fails on a missing crate</a></h4>
+<p>Reserve the crate as above, using the <code>0.0.0</code> placeholder and never the release version.</p>
+<p>Then check the failed run's log for <code>Uploaded</code> lines to see which crates were already published, since cargo uploads crates one at a time in dependency order.</p>
+<ul>
+<li>If nothing was uploaded, re-run the failed workflow run from the GitHub Actions UI. Re-running keeps the original tag as the workflow ref.</li>
+<li>If some crates were uploaded, publish the rest from a clean checkout of the release tag, excluding each crate that was already published:</li>
+</ul>
+<pre><code class="language-shell">cargo publish --workspace --all-features --exclude <published-crate> --exclude <published-crate>
+</code></pre>
</main>
diff --git a/searchindex.js b/searchindex.js
index a7addadba..aba0b3788 100644
--- a/searchindex.js
+++ b/searchindex.js
@@ -1 +1 @@
-Object.assign(window.search, {"doc_urls":["introduction.html#iceberg-rust","introduction.html#what-is-apache-iceberg","install.html#install","download.html#apache-iceberg-rust-downloads","download.html#releases","download.html#notes","download.html#to-verify-the-signature-of-the-release-artifact","download.html#to-verify-the-checksum-of-the-release-artifact","api.html#catalog","api.html#rest-catalog-apis","api.html#restcatalog","api.html#restsessioncatalog","api.html#table","CONTRIBUTING [...]
\ No newline at end of file
+Object.assign(window.search, {"doc_urls":["introduction.html#iceberg-rust","introduction.html#what-is-apache-iceberg","install.html#install","download.html#apache-iceberg-rust-downloads","download.html#releases","download.html#notes","download.html#to-verify-the-signature-of-the-release-artifact","download.html#to-verify-the-checksum-of-the-release-artifact","api.html#catalog","api.html#rest-catalog-apis","api.html#restcatalog","api.html#restsessioncatalog","api.html#table","CONTRIBUTING [...]
\ No newline at end of file
diff --git a/searchindex.json b/searchindex.json
index 51a754035..0d22f592e 100644
--- a/searchindex.json
+++ b/searchindex.json
@@ -1 +1 @@
-{"doc_urls":["introduction.html#iceberg-rust","introduction.html#what-is-apache-iceberg","install.html#install","download.html#apache-iceberg-rust-downloads","download.html#releases","download.html#notes","download.html#to-verify-the-signature-of-the-release-artifact","download.html#to-verify-the-checksum-of-the-release-artifact","api.html#catalog","api.html#rest-catalog-apis","api.html#restcatalog","api.html#restsessioncatalog","api.html#table","CONTRIBUTING.html#contributing","CONTRIBU [...]
\ No newline at end of file
+{"doc_urls":["introduction.html#iceberg-rust","introduction.html#what-is-apache-iceberg","install.html#install","download.html#apache-iceberg-rust-downloads","download.html#releases","download.html#notes","download.html#to-verify-the-signature-of-the-release-artifact","download.html#to-verify-the-checksum-of-the-release-artifact","api.html#catalog","api.html#rest-catalog-apis","api.html#restcatalog","api.html#restsessioncatalog","api.html#table","CONTRIBUTING.html#contributing","CONTRIBU [...]
\ No newline at end of file