GitHub user potiuk added a comment to the discussion: dag-processor does not show a new version when an import changes
Yes, it is expected. You should use Dag Versioning - for example with GitDagBundle and make sure that this function is in the git repo synced by GitDagBundle - then every time the function changes (new git commit) - even if serialized Dag will be the same - it will create a new version of the Dag - and then every parsing and execution will be associated with the commit version it refers to. GitHub link: https://github.com/apache/airflow/discussions/60900#discussioncomment-15563906 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
