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

potiuk 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 9a38e8c5e3d Add empty version suffix when preparing distributions by 
PMC members (#61352)
9a38e8c5e3d is described below

commit 9a38e8c5e3d880b2eba27d62905109723d13b07c
Author: Jarek Potiuk <[email protected]>
AuthorDate: Tue Feb 3 11:47:07 2026 +0100

    Add empty version suffix when preparing distributions by PMC members 
(#61352)
    
    If VERSION_SUFFIX is exported in the current terminal, it can be
    accidentally used as `--version-suffix` by distribution preparation
    commands - which in case of the PMC verification might cause preparing
    of `PyPI` variants of the distributions, not the `SVN` ones (without
    RC suffix). This PR updates the relevant commands to override the
    suffix with empty suffix - which also is an explicit signal that
    this is intended.
---
 dev/README_RELEASE_AIRFLOW.md    | 8 ++++----
 dev/README_RELEASE_AIRFLOWCTL.md | 2 +-
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/dev/README_RELEASE_AIRFLOW.md b/dev/README_RELEASE_AIRFLOW.md
index b15f1b89147..73b9b2640b9 100644
--- a/dev/README_RELEASE_AIRFLOW.md
+++ b/dev/README_RELEASE_AIRFLOW.md
@@ -795,8 +795,8 @@ git fetch apache --tags
 git checkout ${VERSION_RC}
 export AIRFLOW_REPO_ROOT=$(pwd)
 rm -rf dist/*
-breeze release-management prepare-airflow-distributions --distribution-format 
both
-breeze release-management prepare-task-sdk-distributions --distribution-format 
both
+breeze release-management prepare-airflow-distributions --distribution-format 
both --version-suffix ""
+breeze release-management prepare-task-sdk-distributions --distribution-format 
both --version-suffix ""
 breeze release-management prepare-tarball --tarball-type apache_airflow 
--version ${VERSION} --version-suffix ${VERSION_SUFFIX}
 ```
 
@@ -805,8 +805,8 @@ will be done in a docker container.  However, if you have  
`hatch` installed loc
 `--use-local-hatch` flag and it will build and use  docker image that has 
`hatch` installed.
 
 ```bash
-breeze release-management prepare-airflow-distributions --distribution-format 
both --use-local-hatch
-breeze release-management prepare-task-sdk-distributions --distribution-format 
both --use-local-hatch
+breeze release-management prepare-airflow-distributions --distribution-format 
both --use-local-hatch --version-suffix ""
+breeze release-management prepare-task-sdk-distributions --distribution-format 
both --use-local-hatch --version-suffix ""
 breeze release-management prepare-tarball --tarball-type apache_airflow 
--version ${VERSION} --version-suffix ${VERSION_SUFFIX}
 ```
 
diff --git a/dev/README_RELEASE_AIRFLOWCTL.md b/dev/README_RELEASE_AIRFLOWCTL.md
index 0434346caa6..92d80aca35c 100644
--- a/dev/README_RELEASE_AIRFLOWCTL.md
+++ b/dev/README_RELEASE_AIRFLOWCTL.md
@@ -507,7 +507,7 @@ rm -rf dist/*
 4) Build the packages using checked out sources
 
 ```shell
-breeze release-management prepare-airflow-ctl-distributions 
--distribution-format both
+breeze release-management prepare-airflow-ctl-distributions 
--distribution-format both --version-suffix ""
 breeze release-management prepare-tarball --tarball-type apache_airflow_ctl 
--version "${VERSION}" --version-suffix "${VERSION_SUFFIX}"
 ```
 

Reply via email to