fix(migration): disable disable_sqlite_fkeys for migration 0087 by Lee-W · Pull Request #63256 · apache/airflow

Lee-W · 2026-03-10T10:53:02Z

Why

Due to SQLite's design, we'll need to disable the foreign key constraint for this.

What

Disable SQLite fk constraint

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.

vatsrahul1001 · 2026-03-10T11:50:13Z

@wei, can you fix static checks.

wei · 2026-03-10T11:56:56Z

@wei, can you fix static checks.

cc @Lee-W

Lee-W · 2026-03-10T12:30:00Z

fixed

vatsrahul1001 · 2026-03-10T13:56:44Z

Failures not related to change

github-actions · 2026-03-10T13:58:31Z

Backport failed to create: v3-1-test. View the failure log Run details

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-1-test

You can attempt to backport this manually by running:

cherry_picker bbf2897 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

github-actions · 2026-03-10T13:58:52Z

Hi maintainer, this PR was merged without a milestone set.
We've automatically set the milestone to Airflow 3.1.9 based on: backport label targeting v3-1-test
If this milestone is not correct, please update it to the appropriate milestone.

This comment was generated by Milestone Tag Assistant.

…n 0087 (apache#63256) (cherry picked from commit bbf2897) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

…he#63256) (cherry picked from commit bbf2897)

…) (#63272) (cherry picked from commit bbf2897)

…) (#63272) (cherry picked from commit bbf2897) (cherry picked from commit 0638532)

…he#63256)

Lee-W · 2026-03-10T10:53:02Z

Why

Due to SQLite's design, we'll need to disable the foreign key constraint for this.

What

Disable SQLite fk constraint

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.

vatsrahul1001 · 2026-03-10T11:50:13Z

@wei, can you fix static checks.

wei · 2026-03-10T11:56:56Z

@wei, can you fix static checks.

cc @Lee-W

Lee-W · 2026-03-10T12:30:00Z

fixed

vatsrahul1001 · 2026-03-10T13:56:44Z

Failures not related to change

github-actions · 2026-03-10T13:58:31Z

Backport failed to create: v3-1-test. View the failure log Run details

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-1-test

You can attempt to backport this manually by running:

cherry_picker bbf2897 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

github-actions · 2026-03-10T13:58:52Z

Hi maintainer, this PR was merged without a milestone set.
We've automatically set the milestone to Airflow 3.1.9 based on: backport label targeting v3-1-test
If this milestone is not correct, please update it to the appropriate milestone.

This comment was generated by Milestone Tag Assistant.

…n 0087 (apache#63256) (cherry picked from commit bbf2897) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

…he#63256) (cherry picked from commit bbf2897)

…) (#63272) (cherry picked from commit bbf2897)

…) (#63272) (cherry picked from commit bbf2897) (cherry picked from commit 0638532)

…he#63256)

Lee-W · 2026-03-10T10:53:02Z

Why

Due to SQLite's design, we'll need to disable the foreign key constraint for this.

What

Disable SQLite fk constraint

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.

vatsrahul1001 · 2026-03-10T11:50:13Z

@wei, can you fix static checks.

wei · 2026-03-10T11:56:56Z

@wei, can you fix static checks.

cc @Lee-W

Lee-W · 2026-03-10T12:30:00Z

fixed

vatsrahul1001 · 2026-03-10T13:56:44Z

Failures not related to change

github-actions · 2026-03-10T13:58:31Z

Backport failed to create: v3-1-test. View the failure log Run details

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-1-test

You can attempt to backport this manually by running:

cherry_picker bbf2897 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

github-actions · 2026-03-10T13:58:52Z

Hi maintainer, this PR was merged without a milestone set.
We've automatically set the milestone to Airflow 3.1.9 based on: backport label targeting v3-1-test
If this milestone is not correct, please update it to the appropriate milestone.

This comment was generated by Milestone Tag Assistant.

…n 0087 (apache#63256) (cherry picked from commit bbf2897) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

…he#63256) (cherry picked from commit bbf2897)

…) (#63272) (cherry picked from commit bbf2897)

…) (#63272) (cherry picked from commit bbf2897) (cherry picked from commit 0638532)

…he#63256)

Lee-W · 2026-03-10T10:53:02Z

Why

Due to SQLite's design, we'll need to disable the foreign key constraint for this.

What

Disable SQLite fk constraint

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.

vatsrahul1001 · 2026-03-10T11:50:13Z

@wei, can you fix static checks.

wei · 2026-03-10T11:56:56Z

@wei, can you fix static checks.

cc @Lee-W

Lee-W · 2026-03-10T12:30:00Z

fixed

vatsrahul1001 · 2026-03-10T13:56:44Z

Failures not related to change

github-actions · 2026-03-10T13:58:31Z

Backport failed to create: v3-1-test. View the failure log Run details

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-1-test

You can attempt to backport this manually by running:

cherry_picker bbf2897 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

github-actions · 2026-03-10T13:58:52Z

Hi maintainer, this PR was merged without a milestone set.
We've automatically set the milestone to Airflow 3.1.9 based on: backport label targeting v3-1-test
If this milestone is not correct, please update it to the appropriate milestone.

This comment was generated by Milestone Tag Assistant.

…n 0087 (apache#63256) (cherry picked from commit bbf2897) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

…he#63256) (cherry picked from commit bbf2897)

…) (#63272) (cherry picked from commit bbf2897)

…) (#63272) (cherry picked from commit bbf2897) (cherry picked from commit 0638532)

…he#63256)

Lee-W · 2026-03-10T10:53:02Z

Why

Due to SQLite's design, we'll need to disable the foreign key constraint for this.

What

Disable SQLite fk constraint

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.

vatsrahul1001 · 2026-03-10T11:50:13Z

@wei, can you fix static checks.

wei · 2026-03-10T11:56:56Z

@wei, can you fix static checks.

cc @Lee-W

Lee-W · 2026-03-10T12:30:00Z

fixed

vatsrahul1001 · 2026-03-10T13:56:44Z

Failures not related to change

github-actions · 2026-03-10T13:58:31Z

Backport failed to create: v3-1-test. View the failure log Run details

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-1-test

You can attempt to backport this manually by running:

cherry_picker bbf2897 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

github-actions · 2026-03-10T13:58:52Z

Hi maintainer, this PR was merged without a milestone set.
We've automatically set the milestone to Airflow 3.1.9 based on: backport label targeting v3-1-test
If this milestone is not correct, please update it to the appropriate milestone.

This comment was generated by Milestone Tag Assistant.

…n 0087 (apache#63256) (cherry picked from commit bbf2897) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

…he#63256) (cherry picked from commit bbf2897)

…) (#63272) (cherry picked from commit bbf2897)

…) (#63272) (cherry picked from commit bbf2897) (cherry picked from commit 0638532)

…he#63256)

Lee-W · 2026-03-10T10:53:02Z

Why

Due to SQLite's design, we'll need to disable the foreign key constraint for this.

What

Disable SQLite fk constraint

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.

vatsrahul1001 · 2026-03-10T11:50:13Z

@wei, can you fix static checks.

wei · 2026-03-10T11:56:56Z

@wei, can you fix static checks.

cc @Lee-W

Lee-W · 2026-03-10T12:30:00Z

fixed

vatsrahul1001 · 2026-03-10T13:56:44Z

Failures not related to change

github-actions · 2026-03-10T13:58:31Z

Backport failed to create: v3-1-test. View the failure log Run details

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-1-test

You can attempt to backport this manually by running:

cherry_picker bbf2897 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

github-actions · 2026-03-10T13:58:52Z

Hi maintainer, this PR was merged without a milestone set.
We've automatically set the milestone to Airflow 3.1.9 based on: backport label targeting v3-1-test
If this milestone is not correct, please update it to the appropriate milestone.

This comment was generated by Milestone Tag Assistant.

…n 0087 (apache#63256) (cherry picked from commit bbf2897) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

…he#63256) (cherry picked from commit bbf2897)

…) (#63272) (cherry picked from commit bbf2897)

…) (#63272) (cherry picked from commit bbf2897) (cherry picked from commit 0638532)

…he#63256)

Lee-W · 2026-03-10T10:53:02Z

Why

Due to SQLite's design, we'll need to disable the foreign key constraint for this.

What

Disable SQLite fk constraint

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.

vatsrahul1001 · 2026-03-10T11:50:13Z

@wei, can you fix static checks.

wei · 2026-03-10T11:56:56Z

@wei, can you fix static checks.

cc @Lee-W

Lee-W · 2026-03-10T12:30:00Z

fixed

vatsrahul1001 · 2026-03-10T13:56:44Z

Failures not related to change

github-actions · 2026-03-10T13:58:31Z

Backport failed to create: v3-1-test. View the failure log Run details

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-1-test

You can attempt to backport this manually by running:

cherry_picker bbf2897 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

github-actions · 2026-03-10T13:58:52Z

Hi maintainer, this PR was merged without a milestone set.
We've automatically set the milestone to Airflow 3.1.9 based on: backport label targeting v3-1-test
If this milestone is not correct, please update it to the appropriate milestone.

This comment was generated by Milestone Tag Assistant.

…n 0087 (apache#63256) (cherry picked from commit bbf2897) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

…he#63256) (cherry picked from commit bbf2897)

…) (#63272) (cherry picked from commit bbf2897)

…) (#63272) (cherry picked from commit bbf2897) (cherry picked from commit 0638532)

…he#63256)

Lee-W · 2026-03-10T10:53:02Z

Why

Due to SQLite's design, we'll need to disable the foreign key constraint for this.

What

Disable SQLite fk constraint

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.

vatsrahul1001 · 2026-03-10T11:50:13Z

@wei, can you fix static checks.

wei · 2026-03-10T11:56:56Z

@wei, can you fix static checks.

cc @Lee-W

Lee-W · 2026-03-10T12:30:00Z

fixed

vatsrahul1001 · 2026-03-10T13:56:44Z

Failures not related to change

github-actions · 2026-03-10T13:58:31Z

Backport failed to create: v3-1-test. View the failure log Run details

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-1-test

You can attempt to backport this manually by running:

cherry_picker bbf2897 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

github-actions · 2026-03-10T13:58:52Z

Hi maintainer, this PR was merged without a milestone set.
We've automatically set the milestone to Airflow 3.1.9 based on: backport label targeting v3-1-test
If this milestone is not correct, please update it to the appropriate milestone.

This comment was generated by Milestone Tag Assistant.

…n 0087 (apache#63256) (cherry picked from commit bbf2897) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

…he#63256) (cherry picked from commit bbf2897)

…) (#63272) (cherry picked from commit bbf2897)

…) (#63272) (cherry picked from commit bbf2897) (cherry picked from commit 0638532)

…he#63256)

Lee-W requested a review from ephraimbuddy as a code owner March 10, 2026 10:53

boring-cyborgBot added the area:db-migrations PRs with DB migration label Mar 10, 2026

Lee-W added the backport-to-v3-1-test label Mar 10, 2026

fix(migration): disable disable_sqlite_fkeys for migration 0087
636dc1e

Lee-W force-pushed the fix-0087-migration branch from cfc2244 to 636dc1eCompare March 10, 2026 12:29

ephraimbuddy approved these changes Mar 10, 2026
View reviewed changes

vatsrahul1001 approved these changes Mar 10, 2026
View reviewed changes

phanikumv approved these changes Mar 10, 2026
View reviewed changes

vatsrahul1001 merged commit bbf2897 into apache:mainMar 10, 2026
161 of 164 checks passed

vatsrahul1001 deleted the fix-0087-migration branch March 10, 2026 13:56

github-actionsBot added this to the Airflow 3.1.9 milestone Mar 10, 2026

Lee-W added a commit to astronomer/airflow that referenced this pull request Mar 10, 2026
[v3-1-test] fix(migration): disable disable_sqlite_fkeys for migratio…
f8901c5
…n 0087 (apache#63256) (cherry picked from commit bbf2897) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

vatsrahul1001 modified the milestones: Airflow 3.1.9, Airflow 3.1.8 Mar 10, 2026

Lee-W added a commit to astronomer/airflow that referenced this pull request Mar 10, 2026
fix(migration): disable disable_sqlite_fkeys for migration 0087 (apac…
c37baaf
…he#63256) (cherry picked from commit bbf2897)

vatsrahul1001 pushed a commit that referenced this pull request Mar 10, 2026
fix(migration): disable disable_sqlite_fkeys for migration 0087 (#63256…
0638532
…) (#63272) (cherry picked from commit bbf2897)

vatsrahul1001 pushed a commit that referenced this pull request Mar 10, 2026
fix(migration): disable disable_sqlite_fkeys for migration 0087 (#63256…
3476670
…) (#63272) (cherry picked from commit bbf2897) (cherry picked from commit 0638532)

dominikhei pushed a commit to dominikhei/airflow that referenced this pull request Mar 11, 2026
fix(migration): disable disable_sqlite_fkeys for migration 0087 (apac…
e546623
…he#63256)

Pyasma pushed a commit to Pyasma/airflow that referenced this pull request Mar 13, 2026
fix(migration): disable disable_sqlite_fkeys for migration 0087 (apac…
c3c1ac7
…he#63256)