Skip to content

Fix documentation misusing previous/next for task relationships - #69179

Merged
eladkal merged 1 commit into
apache:mainfrom
FrankYang0529:airflow-previous-to-upstream
Jul 7, 2026
Merged

Fix documentation misusing previous/next for task relationships#69179
eladkal merged 1 commit into
apache:mainfrom
FrankYang0529:airflow-previous-to-upstream

Conversation

@FrankYang0529

Copy link
Copy Markdown
Member

Based on Relationship Terminology, the upstream/downstream is used in a same dag run and previous/next is used in a same task between different data intervals. Fix document which misuses previous/next for task relationships.


Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {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.

Signed-off-by: PoAn Yang <payang@apache.org>
@FrankYang0529
FrankYang0529 marked this pull request as ready for review July 1, 2026 07:45
@FrankYang0529
FrankYang0529 requested a review from o-nikolas as a code owner July 1, 2026 07:45
@Lee-W Lee-W added the backport-to-v3-3-test Backport to v3-3-test label Jul 1, 2026
@eladkal eladkal added this to the Airflow 3.3.1 milestone Jul 7, 2026
@eladkal
eladkal merged commit a050861 into apache:main Jul 7, 2026
133 checks passed
@github-actions

github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Backport successfully created: v3-3-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-3-test PR Link

github-actions Bot pushed a commit to aws-mwaa/upstream-to-airflow that referenced this pull request Jul 7, 2026
…nships (apache#69179)

(cherry picked from commit a050861)

Co-authored-by: PoAn Yang <payang@apache.org>
Signed-off-by: PoAn Yang <payang@apache.org>
aws-airflow-bot pushed a commit to aws-mwaa/upstream-to-airflow that referenced this pull request Jul 7, 2026
…nships (apache#69179)

(cherry picked from commit a050861)

Co-authored-by: PoAn Yang <payang@apache.org>
Signed-off-by: PoAn Yang <payang@apache.org>
@FrankYang0529
FrankYang0529 deleted the airflow-previous-to-upstream branch July 7, 2026 23:57
potiuk pushed a commit that referenced this pull request Jul 8, 2026
…nships (#69179) (#69570)

(cherry picked from commit a050861)

Signed-off-by: PoAn Yang <payang@apache.org>
Co-authored-by: PoAn Yang <payang@apache.org>
vatsrahul1001 pushed a commit that referenced this pull request Jul 9, 2026
…nships (#69179) (#69570)

(cherry picked from commit a050861)

Signed-off-by: PoAn Yang <payang@apache.org>
Co-authored-by: PoAn Yang <payang@apache.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants