Sync v3-0-stable with 3.0.5rc3 changes
#54622
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
…from secrets backends (apache#54574) (cherry picked from commit 1f4c55c)
…ers (apache#54612) Somewhat annoyingly it has to be `sync_to_async(mask_secret)` but that is unavoidable unfortunately. Similar to apache#54574, but for the trigger. (cherry picked from commit a2bd625)
…apache#54614) We are building a small image for our release process to build our distributions in an isolated environment - and this image fails to build on ARM because there are no corresponding binary wheels released for `prek` so prek is built from sources when installed in this image. This image originally did not have build-essential which is needed in order to compile some of prek dependencies. This PR temporary adds build-essential until prek will produce more binary wheels for more target platforms. This is tracked in j178/prek#451 (cherry picked from commit 50c1941) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
…pache#54464) (apache#54473) When airflow package inventories cannot be downloaded (for example because they were deleted) we can always rebuild them locally from sources. This might happen for example when our "main" developer documentation published in `apache-airflow-docs` is accidentally or purposefully deleted (for example to refresh it from scratch). This can also happen when we have a new provider and it has never been published, or when we add new distribution that has not yet had a documentation built (such as task-sdk, or airflowctl in the future). This PR updates the existing mechanism to: * not only handle missing "apache-airflow-" packages but also the other airflow packages that do not follow this naming convention * adds better diagnostics so that if we miss to add a distribution in the future we know what to do (cherry picked from commit 8d311c7) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
…ache#54542) (apache#54546) This test was previously creating and running 40 tasks, when all we actually need to do is to put the DB in the state we expect (RTIF rows exist) and then run one task. This takes the test time form 31s down to 4s. This was tested that it still correctly tests the correct behaviour by removing the `session.flush()` that was added in the same change where this test was added, apache#42928 / ced319f. (cherry picked from commit 5a411d7) Co-authored-by: Ash Berlin-Taylor <ash@apache.org>
boring-cyborg
bot
added
area:API
kaxil
requested review from
amoghrajesh,
ashb,
dstandish,
eladkal,
ephraimbuddy,
gopidesupavan,
hussein-awala,
jedcunningham and
potiuk
as code owners
ashb
approved these changes
Aug 18, 2025
sunank200
approved these changes
Aug 18, 2025
jedcunningham
approved these changes
Aug 18, 2025
amoghrajesh
approved these changes
Aug 18, 2025
potiuk
approved these changes
Aug 18, 2025
Member
|
We have also |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 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.
User-facing changes from rc2:
^ 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.