docs(plugins_manager): fix misleading typo by Lee-W · Pull Request #67101 · apache/airflow

Lee-W · 2026-05-18T10:10:34Z

Why

Found one misleading typo during PR reviewing.

What

fix the typo

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.

jason810496

Nice catch!

Lee-W · 2026-05-18T10:18:00Z

Thanks Jarek for the deadline alert PR

github-actions · 2026-05-18T13:48:19Z

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

This comment was generated by Milestone Tag Assistant.

github-actions · 2026-05-18T13:48:54Z

Backport successfully created: v3-2-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-2-test

(cherry picked from commit aab7417) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

Lee-W · 2026-05-18T10:10:34Z

Why

Found one misleading typo during PR reviewing.

What

fix the typo

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.

jason810496

Nice catch!

Lee-W · 2026-05-18T10:18:00Z

Thanks Jarek for the deadline alert PR

github-actions · 2026-05-18T13:48:19Z

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

This comment was generated by Milestone Tag Assistant.

github-actions · 2026-05-18T13:48:54Z

Backport successfully created: v3-2-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-2-test

(cherry picked from commit aab7417) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

Lee-W · 2026-05-18T10:10:34Z

Why

Found one misleading typo during PR reviewing.

What

fix the typo

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.

jason810496

Nice catch!

Lee-W · 2026-05-18T10:18:00Z

Thanks Jarek for the deadline alert PR

github-actions · 2026-05-18T13:48:19Z

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

This comment was generated by Milestone Tag Assistant.

github-actions · 2026-05-18T13:48:54Z

Backport successfully created: v3-2-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-2-test

(cherry picked from commit aab7417) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

Lee-W · 2026-05-18T10:10:34Z

Why

Found one misleading typo during PR reviewing.

What

fix the typo

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.

jason810496

Nice catch!

Lee-W · 2026-05-18T10:18:00Z

Thanks Jarek for the deadline alert PR

github-actions · 2026-05-18T13:48:19Z

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

This comment was generated by Milestone Tag Assistant.

github-actions · 2026-05-18T13:48:54Z

Backport successfully created: v3-2-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-2-test

(cherry picked from commit aab7417) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

Lee-W · 2026-05-18T10:10:34Z

Why

Found one misleading typo during PR reviewing.

What

fix the typo

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.

jason810496

Nice catch!

Lee-W · 2026-05-18T10:18:00Z

Thanks Jarek for the deadline alert PR

github-actions · 2026-05-18T13:48:19Z

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

This comment was generated by Milestone Tag Assistant.

github-actions · 2026-05-18T13:48:54Z

Backport successfully created: v3-2-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-2-test

(cherry picked from commit aab7417) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

Lee-W · 2026-05-18T10:10:34Z

Why

Found one misleading typo during PR reviewing.

What

fix the typo

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.

jason810496

Nice catch!

Lee-W · 2026-05-18T10:18:00Z

Thanks Jarek for the deadline alert PR

github-actions · 2026-05-18T13:48:19Z

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

This comment was generated by Milestone Tag Assistant.

github-actions · 2026-05-18T13:48:54Z

Backport successfully created: v3-2-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-2-test

(cherry picked from commit aab7417) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

Lee-W · 2026-05-18T10:10:34Z

Why

Found one misleading typo during PR reviewing.

What

fix the typo

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.

jason810496

Nice catch!

Lee-W · 2026-05-18T10:18:00Z

Thanks Jarek for the deadline alert PR

github-actions · 2026-05-18T13:48:19Z

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

This comment was generated by Milestone Tag Assistant.

github-actions · 2026-05-18T13:48:54Z

Backport successfully created: v3-2-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-2-test

(cherry picked from commit aab7417) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

Lee-W · 2026-05-18T10:10:34Z

Why

Found one misleading typo during PR reviewing.

What

fix the typo

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.

jason810496

Nice catch!

Lee-W · 2026-05-18T10:18:00Z

Thanks Jarek for the deadline alert PR

github-actions · 2026-05-18T13:48:19Z

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

This comment was generated by Milestone Tag Assistant.

github-actions · 2026-05-18T13:48:54Z

Backport successfully created: v3-2-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-2-test

(cherry picked from commit aab7417) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

docs(plugins_manager): fix misleading typo
485ce3e

Lee-W requested review from amoghrajesh, ashb and potiuk as code owners May 18, 2026 10:10

Lee-W requested a review from jason810496 May 18, 2026 10:10

jason810496 approved these changes May 18, 2026
View reviewed changes

amoghrajesh approved these changes May 18, 2026
View reviewed changes

choo121600 approved these changes May 18, 2026
View reviewed changes

Lee-W added the backport-to-v3-2-test label May 18, 2026

Lee-W merged commit aab7417 into apache:mainMay 18, 2026
78 checks passed

Lee-W deleted the fix-partition-mappers-comment branch May 18, 2026 13:47

github-actionsBot added this to the Airflow 3.2.3 milestone May 18, 2026

github-actionsBot pushed a commit to aws-mwaa/upstream-to-airflow that referenced this pull request May 18, 2026
[v3-2-test] docs(plugins_manager): fix misleading typo (apache#67101)
a05eb89
(cherry picked from commit aab7417) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

vatsrahul1001 modified the milestones: Airflow 3.2.3, Airflow 3.2.2 May 18, 2026

aws-airflow-bot pushed a commit to aws-mwaa/upstream-to-airflow that referenced this pull request May 18, 2026
[v3-2-test] docs(plugins_manager): fix misleading typo (apache#67101)
2aef361
(cherry picked from commit aab7417) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

potiuk pushed a commit that referenced this pull request May 18, 2026
[v3-2-test] docs(plugins_manager): fix misleading typo (#67101) (#67114)
acae4fe
(cherry picked from commit aab7417) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

vatsrahul1001 pushed a commit that referenced this pull request May 20, 2026
[v3-2-test] docs(plugins_manager): fix misleading typo (#67101) (#67114)
9d80770
(cherry picked from commit aab7417) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

vatsrahul1001 pushed a commit that referenced this pull request May 20, 2026
[v3-2-test] docs(plugins_manager): fix misleading typo (#67101) (#67114)
6c4980a
(cherry picked from commit aab7417) Co-authored-by: Wei Lee <weilee.rx@gmail.com>

vatsrahul1001 pushed a commit that referenced this pull request May 21, 2026
[v3-2-test] docs(plugins_manager): fix misleading typo (#67101) (#67114)
e8244c6
(cherry picked from commit aab7417) Co-authored-by: Wei Lee <weilee.rx@gmail.com>