Dbt Core End of Life Dates
other
Developers rely on Dbt Core for managing and tracking end-of-life dates, supported versions, and security patch timelines, which simplifies the process of planning upgrades and ensuring the continued support of their projects. Created to address the need for a centralized platform to monitor the lifecycle of software releases, Dbt Core is maintained by a team dedicated to providing accurate and up-to-date information. With its inception, Dbt Core has become an essential tool for developers seeking to stay informed about the status of their dependencies and make informed decisions about when to upgrade or replace them.
The end-of-life landscape for Dbt Core is characterized by a total of 12 versions, with 10 of these having already reached the end of their support lifecycle. Currently, only 2 versions remain active, with the latest stable version being 1.11.11. As the landscape continues to evolve, developers should be aware that the next version to reach end-of-life is 1.10, scheduled for June 16, 2026. This information is crucial for planning and ensuring a seamless transition to a supported version. The most recent end-of-life date was December 9, 2025, for version 1.9, highlighting the ongoing need for vigilance in tracking the lifecycle of Dbt Core releases.
Given the current security picture, Dbt Core has a clean slate with 0 tracked CVEs and 0 critical vulnerabilities. As a result, there is no most affected version, and no Known Exploited Vulnerabilities (KEV) status is applicable. This favorable security posture is a testament to the robustness of Dbt Core. Nevertheless, developers should remain proactive and continue to monitor the situation, as the security landscape is constantly evolving. By staying informed and taking timely action, developers can ensure the security and integrity of their projects, leveraging Dbt Core as a trusted resource for tracking end-of-life dates and security patch timelines.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 1.11 | Dec 19, 2025 | — | Dec 19, 2026 | in 148d | 1.11.12 | — | Active | |
| 1.10 | Jun 16, 2025 | Dec 19, 2025 | Jun 16, 2026 | 38d ago | 1.10.22 | — | EOL | |
| 1.9 | Dec 9, 2024 | Jun 16, 2025 | Dec 9, 2025 | 227d ago | 1.9.10 | — | EOL | |
| 1.8 | May 9, 2024 | Dec 9, 2024 | May 9, 2025 | 441d ago | 1.8.9 | — | EOL | |
| 1.7 | Nov 2, 2023 | May 9, 2024 | Nov 2, 2024 | 629d ago | 1.7.19 | — | EOL | |
| 1.6 | Jul 31, 2023 | Nov 2, 2023 | Jul 30, 2024 | 724d ago | 1.6.18 | — | EOL | |
| 1.5 | Apr 27, 2023 | Jul 31, 2023 | Apr 27, 2024 | 818d ago | 1.5.11 | — | EOL | |
| 1.4 | Jan 25, 2023 | Apr 27, 2023 | Jan 25, 2024 | 911d ago | 1.4.9 | — | EOL | |
| 1.3 | Oct 11, 2022 | Jan 25, 2023 | Oct 12, 2023 | 1016d ago | 1.3.7 | — | EOL | |
| 1.2 | Jul 26, 2022 | Oct 12, 2022 | Jul 26, 2023 | 1094d ago | 1.2.6 | — | EOL | |
| 1.1 | Apr 28, 2022 | Jul 26, 2022 | Apr 28, 2023 | 1183d ago | 1.1.5 | — | EOL | |
| 1.0 | Dec 3, 2021 | Apr 28, 2022 | Dec 3, 2022 | 1329d ago | 1.0.9 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
