This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch v3-3-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/v3-3-test by this push:
new 5c633f97ef9 [v3-3-test] Clarify provider release verification steps
(#69577) (#69618)
5c633f97ef9 is described below
commit 5c633f97ef9181c77d2d92b685b38a13a2a47019
Author: github-actions[bot]
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Mon Jul 13 01:58:05 2026 +0200
[v3-3-test] Clarify provider release verification steps (#69577) (#69618)
While running through the steps today I noticed a few small
things to fix:
- Clarify wording provider release SVN check
- Drop duplicate cd in verification steps
(cherry picked from commit 478f25e10663bbe4bc748cc08fbced6da85db693)
Co-authored-by: Niko Oliveira <[email protected]>
---
dev/README_RELEASE_PROVIDERS.md | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/dev/README_RELEASE_PROVIDERS.md b/dev/README_RELEASE_PROVIDERS.md
index 0237a4342a3..5c1443cee2b 100644
--- a/dev/README_RELEASE_PROVIDERS.md
+++ b/dev/README_RELEASE_PROVIDERS.md
@@ -1096,9 +1096,11 @@ cd asf-dist/dev/airflow
export PATH_TO_AIRFLOW_SVN=$(pwd -P)
```
-Optionally you can use the `breeze release-management check-release-files`
command
-to verify that all expected files are present in SVN. This command will
produce a `Dockerfile.pmc` which
-may help with verifying installation of the packages.
+Verify that all expected files are present in SVN. You can do this manually by
inspecting the
+directory listing against the file counts described above, but the recommended
way is to run the
+`breeze release-management check-release-files` command below, which checks
completeness for you
+(it is the same gate the release manager runs before sending the vote email).
As a bonus it produces
+a `Dockerfile.pmc` which helps with verifying installation of the packages.
Once you have cloned/updated the SVN repository, copy the PyPi URLs shared
in the email to a file called `packages.txt` in the `$AIRFLOW_REPO_ROOT/files`
@@ -1132,7 +1134,7 @@ it means that the build has a verified provenance.
How to verify it:
-1) Change directory where your airflow sources are checked out
+1) Change directory to where your airflow sources are checked out:
```shell
cd "$AIRFLOW_REPO_ROOT"
@@ -1141,7 +1143,6 @@ cd "$AIRFLOW_REPO_ROOT"
2) Check out the ``providers/YYYY-MM-DD`` tag:
```shell
-cd "$AIRFLOW_REPO_ROOT"
git fetch upstream --tags
git checkout providers/${RELEASE_DATE}
```
