Skip to content
Immediate Team Action Required
Direct all Airflow DAG owners to complete their Python 3.12 migration immediately.
This is a mandatory prerequisite for Airflow 3 enablement and continued job execution.Python 3.9 End of Life (Passed on Oct 31, 2025)
Jobs still running on Python 3.9 are now non-compliant and at risk of failure during upcoming platform transitions.Migration Window (Jan – Mar 2026)
Airflow 3 migrations will occur in coordinated waves during this period.
The Airflow Product Team will reach out to directors and managers to secure commitments and align schedules for each team.Visibility & Accountability
A complete 🔗 lists each DAG, owner, team, and management chain to help identify impacted jobs and track migration progress.Platform Objectives
The Airflow 3 upgrade improves scalability, reliability, and governance across Discover’s data ecosystem — preparing the platform for future AI, ML, data stream and advanced data orchestration workloads.
Identify your Python DAGs: Identify your team, members & DAGs from which needs to be updated to Python 3.12 runtime in Airflow.Refactor & Test in Airflow Dev (3.12 image available): Validate workflows and dependencies.Schedule your Promotion & migration: Submit a for DAGs to promote to Python 3.12 runtime & migrate to Airflow 3 (Jan 2025).Monitor & Validate: Confirm DAG success post upgrade & migration; remediate any failures promptly.
🔗 Python 3.12 Image in Airflow 2: Available since April 7, 2025
Reference: “” — Airflow Support Group > Announcements | Teams🆘 : Open tickets for runtime upgrade, Airflow 3 migration, issues, testing, planning, or scheduling assistanceMigration timelineRequired user actionsSupport channels and resources
Share
Explore
DFS Airflow Python 3.12 & Airflow 3 Migration guide
Hi all Airflow users & their leaders!
From: Airflow Product Team
Date: November 7, 2025
Overview
Discover’s Airflow 3 migration program is now entering its execution phase.
To ensure workflow continuity and compliance, all Python-based Airflow DAGs must migrate to Python 3.12.
Python 3.9 reached end of life on October 31, 2025 and is no longer supported under Discover’s cybersecurity or technology standards.
To maintain reliability and support the Airflow 3 rollout, all DAG owners must ensure their Python jobs are compatible with Python 3.12.
Executive Summary for Leadership
Migration Overview
🗓️ Period
🚩 Milestone
📋 Details
🗓️ Period
🚩 Milestone
📋 Details
April 2025
Python 3.12 available in Airflow Dev
✅ Completed — Teams may already test and validate DAGs
October 2025
Python 3.9 End of Life
🔒 Python 3.9 is now unsupported and non-compliant
Mid December 2025
Airflow 3 Production Available
🚀 Airflow 3 environment goes live for migration readiness
Jan – Mar 2026
Airflow 3 Migration Waves
⚙️ Migrations will occur in scheduled waves; the Airflow team will coordinate with each group
Post-Migration
April 22, 2026
Airflow 2 Decommission
🛑 Airflow 2 EOL, Platform will be retired after all workloads are successfully transitioned
There are no rows in this table
🔧 What You Need to Do
Support & Resources
User Information Sessions
To ensure alignment, we are offering two information sessions for all users, managers, and directors. Invitations to follow.
Attendees are encouraged to choose only one:
Topics Covered:
🛡️ Compliance Note
Jobs remaining on Python 3.9 are now non-compliant and may fail after the Airflow 3 cutover.
Ensure all DAGs are Python 3.12 compatible before February 17, 2026 to avoid production disruptions.
Thank you for your partnership and swift action.
Together we will complete a secure, governed, and compliant Airflow 3 transition.
— Discover Airflow Platform Product Team
Product Lead: Gaurav Gaikwad
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.