You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "github-actions[bot] (via GitHub)" <gi...@apache.org> on 2026/10/20 23:06:17 UTC
[PR] [v3-4-test] Fix task Clear and callback bundles after code-only Dag changes (#73915) [airflow]
github-actions[bot] opened a new pull request, #75256:
URL: https://github.com/apache/airflow/pull/75256
* Fix task Clear bundle selection after code-only Dag changes
A deployed callable fix can leave serialization unchanged while an existing
run stays pinned to an older bundle. Users need the latest-version clear
option to remain available and an explicit selection to take effect for
active runs. Scheduler callbacks also need to resolve the same bundle as
task execution.
* Pair task callback bundle manifest with the run's pinned version
Callbacks and failure emails resolve their bundle version from the Dag run,
but the manifest still came from the task instance's Dag version. When that
version differs from the one the run was created with, a manifest-based
bundle would initialize the run's bundle version from another version's
manifest. Task execution and Dag-run callbacks already take both from the
run's pinned version.
* Run triggerer task callbacks on the run's pinned bundle
A deferred task that finishes in the triggerer has its callback sent from
there, and that path still took the bundle from the task instance's Dag
version. A code-only update advances that version's bundle in place while
the run stays pinned, so the callback would run newer code than the task
did. Scheduler callbacks already resolve the bundle from the run.
* Stop pairing a pinned bundle with an overwritten manifest
A code-only update reuses the Dag version and overwrites its bundle version
and manifest in place, while existing runs stay pinned to the older bundle
version. Task execution and callbacks then shipped the run's older version
with the newer manifest, so a manifest-based bundle would materialize code
the run was never pinned to. Once the original manifest is gone, sending
none is safer than sending one for a different version.
(cherry picked from commit 05981d3e2aaa2a4ac4aa5c9a5fba350459b5803b)
Co-authored-by: Dheeraj Turaga <dh...@gmail.com>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] [v3-4-test] Fix task Clear and callback bundles after code-only Dag changes (#73915) [airflow]
Posted by "vatsrahul1001 (via GitHub)" <gi...@apache.org>.
vatsrahul1001 merged PR #75256:
URL: https://github.com/apache/airflow/pull/75256
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] [v3-4-test] Fix task Clear and callback bundles after code-only Dag changes (#73915) [airflow]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #75256:
URL: https://github.com/apache/airflow/pull/75256#issuecomment-6316110448
Hi maintainer, this PR was merged without a milestone set.
We've automatically set the milestone to **[Airflow 3.4.1](https://github.com/apache/airflow/milestone/154)** based on: bug fix merged to version branch
If this milestone is not correct, please update it to the appropriate milestone.
> This comment was generated by [Milestone Tag Assistant](https://github.com/apache/airflow/blob/main/.github/workflows/milestone-tag-assistant.yml).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org