[amoghrajesh]

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

What

#75405 added task-sdk/docs/task-handler.rst and linked to it from the yaml Dags guide with :doc:task-sdk:task-handler``. That page has not been published yet hence CI fails.

Current behaviour

When a PR builds only the apache-airflow docs, sphinx checks the link against the published task-sdk docs. The page is not there yet, so the docs build fails with:

yaml-dags.rst:426: WARNING: unknown document: 'task-sdk:task-handler'

Any airflow-core PR that builds docs hits this (for example #76376). #75405 passed because it changed both packages, so CI built both doc sets together.

Proposed change

Replace the :doc: link with a plain URL to the task SDK task handler page. public-airflow-interface.rst already links to the Task SDK this way.

What's next

The URL returns a 404 until the next task-sdk release publishes the page. After that, it can go back to :doc:task-sdk:task-handler``.

---

• 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.

[pierrejeambrun]

LGTM.

Probably a todo or something could be good not to forget to revert this to the :doc: idiom once the page is published.