Update release documentation for airflowctl and tarballs by potiuk · Pull Request #57337 · apache/airflow

potiuk · 2025-10-27T09:31:03Z

With airflowctl release, we are updating the release process as this is the first time we release the package. That also includes preparing source package - for airflowctl but also providers (in the future for task-sdk as well).

This PR is the next step in making our release process more complete with sources released every time we release all packages.

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

With airflowctl release, we are updating the release process as this is the first time we release the package. That also includes preparing source package - for airflowctl but also providers (in the future for task-sdk as well). This PR is the next step in making our release process more complete with sources released every time we release all packages.

potiuk · 2025-10-27T09:43:37Z

I need that one merged to annnounce the RC for airflow-ctl.

potiuk · 2025-10-27T10:03:49Z

Related issue: #47343

potiuk · 2025-10-27T10:04:17Z

The failure is being addressed in #57335

github-actions · 2025-10-27T10:34:45Z

Backport failed to create: v3-1-test. View the failure log Run details

Status	Branch	Result
❌	v3-1-test

You can attempt to backport this manually by running:

cherry_picker e4e74dd v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

bugraoz93 · 2025-10-28T00:27:17Z

Many thanks Jarek! 🙏

There were few typos after recent refactoring (apache#57337): * "airflow" was still the default for distribution name when we changed it to "apache_airflow" * PACKGE_DATE variable in copy-able commands missed A

There were few typos after recent refactoring (#57337): * "airflow" was still the default for distribution name when we changed it to "apache_airflow" * PACKGE_DATE variable in copy-able commands missed A

Tagging providers after release after apache#57337 happened after preparing the tarball - which was wrong :) as tarball uses the tag to build the -sources package. Also it cannot be done too early becasue tags are created based on the provider packages prepared in dist. So - tagging providers *SHOULD* happen between creating provider distributions and creating tarball. This PR moves creation of the tarball to the right place, it also improves a bit the "tag-providers" step: * it uses PACKAGE_DATE environment variable if it is defined * it does not react on existing tags - it simply overwrites the tags if such tags exist.

Tagging providers after release after #57337 happened after preparing the tarball - which was wrong :) as tarball uses the tag to build the -sources package. Also it cannot be done too early becasue tags are created based on the provider packages prepared in dist. So - tagging providers *SHOULD* happen between creating provider distributions and creating tarball. This PR moves creation of the tarball to the right place, it also improves a bit the "tag-providers" step: * it uses PACKAGE_DATE environment variable if it is defined * it does not react on existing tags - it simply overwrites the tags if such tags exist.

…pache#57337) With airflowctl release, we are updating the release process as this is the first time we release the package. That also includes preparing source package - for airflowctl but also providers (in the future for task-sdk as well). This PR is the next step in making our release process more complete with sources released every time we release all packages. (cherry picked from commit e4e74dd) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>

…57337) (#57876) With airflowctl release, we are updating the release process as this is the first time we release the package. That also includes preparing source package - for airflowctl but also providers (in the future for task-sdk as well). This PR is the next step in making our release process more complete with sources released every time we release all packages. (cherry picked from commit e4e74dd)

There were few typos after recent refactoring (apache#57337): * "airflow" was still the default for distribution name when we changed it to "apache_airflow" * PACKGE_DATE variable in copy-able commands missed A

Tagging providers after release after apache#57337 happened after preparing the tarball - which was wrong :) as tarball uses the tag to build the -sources package. Also it cannot be done too early becasue tags are created based on the provider packages prepared in dist. So - tagging providers *SHOULD* happen between creating provider distributions and creating tarball. This PR moves creation of the tarball to the right place, it also improves a bit the "tag-providers" step: * it uses PACKAGE_DATE environment variable if it is defined * it does not react on existing tags - it simply overwrites the tags if such tags exist.

potiuk · 2025-10-27T09:31:03Z

With airflowctl release, we are updating the release process as this is the first time we release the package. That also includes preparing source package - for airflowctl but also providers (in the future for task-sdk as well).

This PR is the next step in making our release process more complete with sources released every time we release all packages.

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

With airflowctl release, we are updating the release process as this is the first time we release the package. That also includes preparing source package - for airflowctl but also providers (in the future for task-sdk as well). This PR is the next step in making our release process more complete with sources released every time we release all packages.

potiuk · 2025-10-27T09:43:37Z

I need that one merged to annnounce the RC for airflow-ctl.

potiuk · 2025-10-27T10:03:49Z

Related issue: #47343

potiuk · 2025-10-27T10:04:17Z

The failure is being addressed in #57335

github-actions · 2025-10-27T10:34:45Z

Backport failed to create: v3-1-test. View the failure log Run details

Status	Branch	Result
❌	v3-1-test

You can attempt to backport this manually by running:

cherry_picker e4e74dd v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

bugraoz93 · 2025-10-28T00:27:17Z