This is an automated email from the ASF dual-hosted git repository.
ephraimanierobi pushed a commit to branch v3-1-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/v3-1-test by this push:
new 25fd5a842f3 [v3-1-test] Fix python client NOTICE and wheel content
(#60539) (#60551)
25fd5a842f3 is described below
commit 25fd5a842f3a5eb76c29b24b90ba2c77e1775770
Author: github-actions[bot]
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Fri Jan 16 09:55:42 2026 +0100
[v3-1-test] Fix python client NOTICE and wheel content (#60539) (#60551)
There were some issues found in the process of Python Client
generation:
* NOTICE file was empty
* The .whl file contained `docs` and `tests` folders needlessly
* Verification steps were not separated out from publishing RC
This PR fixes those problems.
(cherry picked from commit ed62102b558430f7d36d18f0ecaae1a2e9dd5bcd)
Co-authored-by: Jarek Potiuk <[email protected]>
---
clients/python/NOTICE | 5 +++++
clients/python/pyproject.toml | 2 --
dev/README_RELEASE_AIRFLOWCTL.md | 1 -
dev/README_RELEASE_PYTHON_CLIENT.md | 26 ++++++++++++--------------
4 files changed, 17 insertions(+), 17 deletions(-)
diff --git a/clients/python/NOTICE b/clients/python/NOTICE
index e69de29bb2d..a51bd9390d0 100644
--- a/clients/python/NOTICE
+++ b/clients/python/NOTICE
@@ -0,0 +1,5 @@
+Apache Airflow
+Copyright 2016-2026 The Apache Software Foundation
+
+This product includes software developed at
+The Apache Software Foundation (http://www.apache.org/).
diff --git a/clients/python/pyproject.toml b/clients/python/pyproject.toml
index 2cef853a066..35e28149783 100644
--- a/clients/python/pyproject.toml
+++ b/clients/python/pyproject.toml
@@ -94,8 +94,6 @@ include = [
[tool.hatch.build.targets.wheel]
artifacts = [
"/airflow_client",
- "/docs",
- "/test",
"v2.yaml",
]
include = [
diff --git a/dev/README_RELEASE_AIRFLOWCTL.md b/dev/README_RELEASE_AIRFLOWCTL.md
index e036159e721..330ec311930 100644
--- a/dev/README_RELEASE_AIRFLOWCTL.md
+++ b/dev/README_RELEASE_AIRFLOWCTL.md
@@ -433,7 +433,6 @@ Regards,
EOF
```
-
## Verify the release candidate by PMC members
### SVN check
diff --git a/dev/README_RELEASE_PYTHON_CLIENT.md
b/dev/README_RELEASE_PYTHON_CLIENT.md
index 09728e529a2..016fabfab44 100644
--- a/dev/README_RELEASE_PYTHON_CLIENT.md
+++ b/dev/README_RELEASE_PYTHON_CLIENT.md
@@ -24,13 +24,9 @@
- [Release Process](#release-process)
- [Prepare PyPI convenience "RC"
packages](#prepare-pypi-convenience-rc-packages)
- [Prepare Vote email on the Airflow Client release
candidate](#prepare-vote-email-on-the-airflow-client-release-candidate)
-- [Verify the release candidate by PMC
members](#verify-the-release-candidate-by-pmc-members)
- - [SVN check](#svn-check)
- - [Reproducible package check](#reproducible-package-check)
- - [Signature check](#signature-check)
- - [SHA512 checksum check](#sha512-checksum-check)
-- [Verify the release candidate by
Contributors](#verify-the-release-candidate-by-contributors)
- - [Testing with Breeze's start-airflow](#testing-with-breezes-start-airflow)
+- [Verification of the release
candidate](#verification-of-the-release-candidate)
+ - [Verify the release candidate by PMC
members](#verify-the-release-candidate-by-pmc-members)
+ - [Verify the release candidate by
Contributors](#verify-the-release-candidate-by-contributors)
- [Publish the final Apache Airflow client
release](#publish-the-final-apache-airflow-client-release)
- [Summarize the voting for the Apache Airflow client
release](#summarize-the-voting-for-the-apache-airflow-client-release)
- [Publish release to SVN](#publish-release-to-svn)
@@ -316,7 +312,9 @@ Cheers,
EOF
```
-# Verify the release candidate by PMC members
+# Verification of the release candidate
+
+## Verify the release candidate by PMC members
PMC members should verify the releases in order to make sure the release is
following the
[Apache Legal Release Policy](http://www.apache.org/legal/release-policy.html).
@@ -332,7 +330,7 @@ The legal checks include:
* verifying if all the checksums are valid for the release
* verifying if all the sources have correct licences
-## SVN check
+### SVN check
The files should be present in the sub-folder of
[Airflow dist](https://dist.apache.org/repos/dist/dev/airflow/clients/python)
@@ -354,7 +352,7 @@ Or update it if you already checked it out:
svn update .
```
-## Reproducible package check
+### Reproducible package check
Airflow Python client supports reproducible builds, which means that the
packages prepared from the same
sources should produce binary identical packages in reproducible way. You
should check if the packages can be
@@ -496,7 +494,7 @@ For example:
! /CODE_OF_CONDUCT.md
```
-## Signature check
+### Signature check
Make sure you have imported into your GPG the PGP key of the person signing
the release. You can find the valid keys in
[KEYS](https://dist.apache.org/repos/dist/release/airflow/KEYS).
@@ -563,7 +561,7 @@ gpg: There is no indication that the signature
belongs to the owner.
Primary key fingerprint: 1271 7556 040E EF2E EAF1 B9C2 75FC CD0A 25FA 0E4B
```
-## SHA512 checksum check
+### SHA512 checksum check
Run this:
@@ -583,7 +581,7 @@ Checking
apache_airflow-client-2.0.2rc4-py2.py3-none-any.whl.sha512
```
-# Verify the release candidate by Contributors
+## Verify the release candidate by Contributors
This can be done (and we encourage to) by any of the Contributors. In fact,
it's best if the
actual users of Airflow Client test it in their own staging/test
installations. Each release candidate
@@ -594,7 +592,7 @@ release candidate number 1,2,3,....).
Once you install and run Airflow Client, you should perform any verification
you see as necessary to check
that the client works as you expected.
-## Testing with Breeze's start-airflow
+### Testing with Breeze's start-airflow
You can test the client by running the `start-airflow` command from Breeze.
This will start Airflow
and allows you to test the client in a real environment.
