Fix release process for Python Client #58447
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
ephraimbuddy,
gopidesupavan,
jason810496,
jedcunningham,
jscheffl and
kaxil
as code owners
boring-cyborg
bot
added
area:dev-tools
backport-to-v3-1-test
potiuk
force-pushed
the
fix-python-client-release-process
branch
from
65e1054 to
a27b315
Compare
jscheffl
approved these changes
Nov 18, 2025
jscheffl
approved these changes
Nov 18, 2025
The Python Client of ours was released so far without sources, because it was assumed it uses the same sources as Airflow - but it's not necessarily the same and it can be released with a different cadence and using different sources - for example to fix some client-only issues. This PR updates the release process to also include source tarball snapshot as part of the release and updates breeze and release process description to make sure sources are produced and verified.
potiuk
force-pushed
the
fix-python-client-release-process
branch
from
a27b315 to
0b25708
Compare
bugraoz93
approved these changes
Nov 18, 2025
github-actions bot
pushed a commit
that referenced
this pull request
Nov 19, 2025
The Python Client of ours was released so far without sources, because it was assumed it uses the same sources as Airflow - but it's not necessarily the same and it can be released with a different cadence and using different sources - for example to fix some client-only issues. This PR updates the release process to also include source tarball snapshot as part of the release and updates breeze and release process description to make sure sources are produced and verified. (cherry picked from commit dda9d61) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Backport successfully created: v3-1-test
|
potiuk
added a commit
that referenced
this pull request
Nov 19, 2025
The Python Client of ours was released so far without sources, because it was assumed it uses the same sources as Airflow - but it's not necessarily the same and it can be released with a different cadence and using different sources - for example to fix some client-only issues. This PR updates the release process to also include source tarball snapshot as part of the release and updates breeze and release process description to make sure sources are produced and verified. (cherry picked from commit dda9d61) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
ephraimbuddy
pushed a commit
that referenced
this pull request
Nov 19, 2025
The Python Client of ours was released so far without sources, because it was assumed it uses the same sources as Airflow - but it's not necessarily the same and it can be released with a different cadence and using different sources - for example to fix some client-only issues. This PR updates the release process to also include source tarball snapshot as part of the release and updates breeze and release process description to make sure sources are produced and verified. (cherry picked from commit dda9d61) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
aaron-wolmutt
pushed a commit
to aaron-wolmutt/airflow
that referenced
this pull request
Nov 20, 2025
The Python Client of ours was released so far without sources, because it was assumed it uses the same sources as Airflow - but it's not necessarily the same and it can be released with a different cadence and using different sources - for example to fix some client-only issues. This PR updates the release process to also include source tarball snapshot as part of the release and updates breeze and release process description to make sure sources are produced and verified.
Copilot AI
pushed a commit
to jason810496/airflow
that referenced
this pull request
Dec 5, 2025
The Python Client of ours was released so far without sources, because it was assumed it uses the same sources as Airflow - but it's not necessarily the same and it can be released with a different cadence and using different sources - for example to fix some client-only issues. This PR updates the release process to also include source tarball snapshot as part of the release and updates breeze and release process description to make sure sources are produced and verified.
itayweb
pushed a commit
to itayweb/airflow
that referenced
this pull request
Dec 6, 2025
The Python Client of ours was released so far without sources, because it was assumed it uses the same sources as Airflow - but it's not necessarily the same and it can be released with a different cadence and using different sources - for example to fix some client-only issues. This PR updates the release process to also include source tarball snapshot as part of the release and updates breeze and release process description to make sure sources are produced and verified.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Python Client of ours was released so far without sources, because it was assumed it uses the same sources as Airflow - but it's not necessarily the same and it can be released with a different cadence and using different sources - for example to fix some client-only issues.
This PR updates the release process to also include source tarball snapshot as part of the release and updates breeze and release process description to make sure sources are produced and verified.
^ 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.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.