Repository navigation
Conversation
ashb
commented
Oct 7, 2026
|
|
||
| .. towncrier release notes start | ||
|
|
||
| Airflow 3.4.0 (unreleased) |
Member
Author
There was a problem hiding this comment.
@vatsrahul1001 Of especial note for you here:
When we use towncrier to generate the release notes it will create a new 3.4.0 header. Please sort out the duplicate headers and put this note "somewhere appropriate near the top"
kaxil
reviewed
Oct 7, 2026
The downgrade refused whenever XCom_v2 or rendered field data had rows, or any task retried since the upgrade, so a rollback after any real use of 3.4 was impossible. This fixes it, as long as the data can be downgraded non-destructively "as if 3.3 wrote it". This means you might loose data that 3.3 wouldn't have kept for archived tries. Document the cost and caveats in the 3.4.0 release notes.
Clearing a mapped task's upstream archives its map_index -1 placeholder and inserts a new current one. When that placeholder is later promoted to index 0 or deleted, its archived attempts were left without a current attempt, which made the 3.4 downgrade refuse in ordinary use. Delete them at expansion, and only for a placeholder that was retried so the common path adds no query. Also bind the downgrade's owner insert for a task first run after the upgrade, check that refused downgrades leave the schema untouched, make the expansion query-count pin exact, and shorten the release note.
ashb
force-pushed
the
worktree-migration0142-downgrade
branch
from
October 8, 2026 14:42
e71c0b3 to
ad93457
Compare
This branch has not been deployed
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.
The downgrade refused whenever XCom_v2 or rendered field data had rows, or
any task retried since the upgrade, so a rollback after any real use of 3.4
was impossible.
This fixes it, as long as the data can be downgraded non-destructively
"as if 3.3 wrote it". This means you might loose data that 3.3 wouldn't
have kept for archived tries.
Document the cost and caveats in the 3.4.0 release notes.
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.