This is an automated email from the ASF dual-hosted git repository.
jedcunningham pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 1dbbac39c20 Update Helm chart release guide (#62095)
1dbbac39c20 is described below
commit 1dbbac39c204eef352767bece51339a85de3a2b9
Author: Jed Cunningham <[email protected]>
AuthorDate: Tue Feb 17 15:15:48 2026 -0700
Update Helm chart release guide (#62095)
This clarifies the docs publishing and index generation steps.
---
dev/README_RELEASE_HELM_CHART.md | 33 ++++++++++++++++++++-------------
1 file changed, 20 insertions(+), 13 deletions(-)
diff --git a/dev/README_RELEASE_HELM_CHART.md b/dev/README_RELEASE_HELM_CHART.md
index bd63ebaa679..d5b5f038324 100644
--- a/dev/README_RELEASE_HELM_CHART.md
+++ b/dev/README_RELEASE_HELM_CHART.md
@@ -811,24 +811,18 @@ The command does the following:
3. Triggers S3 to GitHub Sync
```shell script
-breeze workflow-run publish-docs --ref <tag> --site-env <staging/live/auto>
helm-chart
+breeze workflow-run publish-docs --ref helm-chart/${VERSION} --site-env live
helm-chart
```
-The `--ref` parameter should be the tag of the release candidate you are
publishing. This should be a
-release tag like `helm-chart/1.1.0`
-
-The `--site-env` parameter should be set to `staging` for pre-release versions
or `live` for final releases.
-The default option is `auto` which should automatically select the right
environment based on the tag name.
+## Update `index.yaml` in airflow-site
-Other available parameters can be found with:
+The `index.yaml` file on the Airflow website allows users to easily add the
Apache Airflow Helm repository with:
-```shell script
-breeze workflow-run publish-docs --help
+```shell
+helm repo add apache-airflow https://airflow.apache.org
```
-## Update `index.yaml` in airflow-site
-
-Regenerate `index.yaml` so it can be added to the Airflow website to allow:
`helm repo add apache-airflow https://airflow.apache.org`.
+To update `index.yaml` for the newly released chart version, follow these
steps:
```shell
git clone https://github.com/apache/airflow-site.git airflow-site
@@ -844,9 +838,22 @@ git push
# and finally open a PR
```
+When the PR is merged, you need to rebuild the docs to invalidate the Fastly
cache.
+
+In order to do it, you need to run the [Build
docs](https://github.com/apache/airflow-site/actions/workflows/build.yml)
+workflow in `airflow-site` repository. Make sure to use `main` branch.
+
+You can check the latest chart version that is in the `index.yaml` with:
+
+```shell
+curl -s https://airflow.apache.org/index.yaml | yq e
'.entries.airflow[0].version' -
+```
+
+You can see when ArtifactHUB will next check for a new version by logging in
and going to the [ArtifactHUB control
panel](https://artifacthub.io/control-panel/repositories).
+
## Wait for ArtifactHUB to discover new release
-As we link out to ArtifactHUB in all of our release communications, we now
wait until ArtifactHUB has discovered the new release. This can take 30 minutes
or so to happen after the index change PR from above is merged.
+As we link out to ArtifactHUB in all of our release communications, we now
wait until ArtifactHUB has discovered the new release. This can take 60 minutes
or longer to happen after the index change PR from above is merged.
## Notify developers of release
