This is an automated email from the ASF dual-hosted git repository.
stevenzwu pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/iceberg.git
The following commit(s) were added to refs/heads/main by this push:
new 7bb0fa243b Docs: Drop manual deploy step from release instructions
(#16495)
7bb0fa243b is described below
commit 7bb0fa243baa0834fcc3fb6ec71524864a7a501f
Author: Steven Zhen Wu <[email protected]>
AuthorDate: Thu May 21 15:10:39 2026 -0700
Docs: Drop manual deploy step from release instructions (#16495)
* Docs: Drop manual deploy step from release instructions
The site-ci GitHub Actions workflow runs make deploy automatically on
any push to main that touches docs/, site/, or format/. Replace the
manual "Release versioned docs and javadoc" step in the release guide
with a note describing the auto-trigger so release managers don't push
to asf-site by hand.
Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
Co-authored-by: Kevin Liu <[email protected]>
Co-authored-by: Kevin Liu <[email protected]>
---
site/README.md | 18 ++----------------
site/docs/how-to-release.md | 11 +++++++----
2 files changed, 9 insertions(+), 20 deletions(-)
diff --git a/site/README.md b/site/README.md
index e14bb361d5..ee702f0309 100644
--- a/site/README.md
+++ b/site/README.md
@@ -174,22 +174,8 @@ make build OFFLINE=true
## Release process
-Deploying the docs is a two-step process:
-
-> [!WARNING]
-> The `make release` directive is currently unavailable as we wanted to
discuss the best way forward on how or if we should automate the release. It
involves taking an existing snapshot of the versioned documentation, and
potentially automerging the [`docs`
branch](https://github.com/apache/iceberg/tree/docs) and the [`javadoc`
branch](https://github.com/apache/iceberg/tree/javadoc) which are independent
from the `main` branch. Once this is complete, we can create a pull request
with an [...]
-
- 1. Release a new version by copying the current `/docs` directory to a new
version directory in the `docs` branch and a new javadoc build in the `javadoc`
branch.
- ```sh
- make release ICEBERG_VERSION=${ICEBERG_VERSION}
- ```
- 1. Build and push the generated site to the `asf-site` branch of [remote
repo](https://github.com/apache/iceberg). This requires committer write
permission.
- ```sh
- # Default remote name is 'origin'
- make deploy
- # Or specify a different remote
- make deploy remote_name=apache
- ```
+For release documentation publishing steps, follow the
+[Documentation Release](docs/how-to-release.md#documentation-release) section
of the release guide.
## Validate Links
diff --git a/site/docs/how-to-release.md b/site/docs/how-to-release.md
index cb50cce622..eca2757c76 100644
--- a/site/docs/how-to-release.md
+++ b/site/docs/how-to-release.md
@@ -356,15 +356,18 @@ cp -R apache-iceberg-1.8.0/site/docs/javadoc/1.8.0 1.8.0
Once this is done, create a PR against the `javadoc` branch, similar to
https://github.com/apache/iceberg/pull/12412.
-#### Release versioned docs and javadoc
-
-Please follow the instructions on the GitHub repository in the [`README.md` in
the `site/`](https://github.com/apache/iceberg/tree/main/site) directory.
-
#### Site update
Submit a PR, following the approach in
https://github.com/apache/iceberg/pull/12242,
to update the Iceberg version, the links to the new version's documentation,
and the release notes.
+Once this PR is merged, the
[`site-ci`](https://github.com/apache/iceberg/blob/main/.github/workflows/site-ci.yml)
+GitHub Actions workflow is automatically triggered for any push to `main` that
touches `docs/`, `site/`,
+or `format/`. The workflow runs `make deploy` to build and push the
documentation site to the `asf-site`
+branch, which publishes the new version's docs and javadoc.
+
+The site will be updated automatically. Manually running `make deploy` is no
longer required as part of the release.
+
# How to Verify a Release
Each Apache Iceberg release is validated by the community by holding a vote. A
community release manager
