Allow direct execution from airflow standalone via uvx#64405
Merged
jscheffl merged 4 commits intoapache:mainfrom Mar 29, 2026
Merged
Allow direct execution from airflow standalone via uvx#64405jscheffl merged 4 commits intoapache:mainfrom
jscheffl merged 4 commits intoapache:mainfrom
Conversation
1 task
jscheffl
force-pushed
the
feature/allow-airflow-call-via-uvx
branch
from
49f5a7c to
0e22b16
Compare
potiuk
reviewed
Mar 29, 2026
potiuk
approved these changes
Mar 29, 2026
jscheffl
force-pushed
the
feature/allow-airflow-call-via-uvx
branch
from
0e22b16 to
dff8d56
Compare
jscheffl
added
the
backport-to-v3-2-test
jscheffl
force-pushed
the
feature/allow-airflow-call-via-uvx
branch
from
dff8d56 to
589d03d
Compare
Backport successfully created: v3-2-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
vatsrahul1001
added a commit
that referenced
this pull request
Mar 30, 2026
…64405) (#64432) * Allow direct execution from airflow standalone via uvx * Fix docsbuild * Revise documentation * Spellcheck fix documentation (cherry picked from commit d71755e) Co-authored-by: Jens Scheffler <95105677+jscheffl@users.noreply.github.com> Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com>
Suraj-kumar00
pushed a commit
to Suraj-kumar00/airflow
that referenced
this pull request
Apr 7, 2026
* Allow direct execution from airflow standalone via uvx * Fix docsbuild * Revise documentation * Spellcheck fix documentation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
I was in discussion with a peer who switched to dagster and he told me "I would reconsider checking with Airflow but it is so complex, if it would be possible to
uvx airflowthat would be cool".So I had a bit of sleep over it and currently you need to use
uvx --from apache-airflow airflow standalone... so not far away. But actually just another name-matching entry point definition is missing making it directly usable via uvx.So this PR proposing to add another script alias and some docs for a jump-start for a local development.
If this is merged and we have a new version published with this a user can directly execute:
uvx apache-airflow standaloneand... boom a minute later the web UI is usable (user just need to grab the admin password from logs... but making this better is another story...)Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.