-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Sync v3-0-stable with 3.0.3rc4 changes
#52975
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
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
) (apache#52896) The task-sdk package did not have full integration with airflow docs: * did not have inventory mapping * did not have a way to refer to it via doc:`task-sdk:` directive 8 did not have a development link from the devel index This PR fixes all that. (cherry picked from commit 244af72)
…dagrun is fetched. (apache#52918) (apache#52919) (cherry picked from commit 671d561) Co-authored-by: Karthikeyan Singaravelan <tir.karthi@gmail.com>
…build deps (apache#52909) (apache#52924) I noticed that we did not have `pre-commit-uv` in the image that was building the distribution packages. Adding it should slightly speed up building such an image for isolated package preparation. The `uv` has been upgraded along the way, also the comment that we should automate updating the versions in release_management_command.py has been removed - because we already have automation in place. The missing pieces were adding "hatch", "pyyaml", "gitpython" and "rich". (cherry picked from commit bbc8f74)
…distributions (apache#52908) (apache#52910) The file might be a left-over from earlier api generation and it is already .gitignored, so it does not appear in the source tarball, but sdist and wheel generation does not look at .gitignored files (for a good reason - we might want to include some generated files in those distributions) - so we should exclude it manually similarly as we already do with node_modules for example. (cherry picked from commit 93f2bcc) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
…pache#52937) (cherry picked from commit 601a06d) Co-authored-by: GPK <gopidesupavan@gmail.com>
…ache#52939) (apache#52941) (cherry picked from commit e880389)
…y imports (apache#52956) (apache#52957) (cherry picked from commit aecfc53) Co-authored-by: GPK <gopidesupavan@gmail.com>
vatsrahul1001
approved these changes
Jul 7, 2025
eladkal
approved these changes
Jul 7, 2025
Member
|
Nice! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area:dev-tools
area:production-image
Production image improvements and fixes
area:providers
area:task-sdk
area:UI
Related to UI/UX. For Frontend Developers.
backport-to-v3-1-test
Mark PR with this label to backport to v3-1-test branch
kind:documentation
provider:standard
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.
Sync
v3-0-stablewith 3.0.3rc4 changesOnly 2 user facing changes:
^ 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.