| [dbt](/handbook/enterprise-data/platform/dbt-guide/) | `1.9.2` | [link](https://docs.getdbt.com/docs/dbt-versions/core#latest-releases) | - [dbt best practices for upgrading](https://docs.getdbt.com/docs/dbt-versions/core#best-practices-for-upgrading)<br>- [Upgrading dbt version](https://gitlab.com/gitlab-data/runbooks/-/blob/main/infrastructure/upgrading_dbt_version.md) | `TBA` | - `Data Platform`<br>- `Analytics Engineers`<br>- `Data Scientists` | Not more than 2 versions behind (beta release excluded) and minimum support level `critical` |
| [airflow](/handbook/enterprise-data/platform/infrastructure/#airflow) | `2.10.5` | [link](https://airflow.apache.org/docs/apache-airflow/stable/installation/supported-versions.html#version-life-cycle) | [Upgrade Plan for Airflow](https://gitlab.com/gitlab-data/analytics/-/work_items/26008) | `TBA` | `Data Platform` | Current version released > 1 year |
| [permifrost](/handbook/enterprise-data/platform/permifrost/) | `0.15.4` | [link](https://gitlab.com/gitlab-data/permifrost) | [Upgrading permifrost version](https://gitlab.com/gitlab-data/permifrost/-/blob/master/RELEASE.md?ref_type=heads) | @rbacovic | `Data Platform` | Not more than 2 versions behind (beta release excluded) |
@@ -254,9 +254,8 @@ The reason for upgrading can be dependent tool/package. For instance, if you pla
> **Table 5:** Log activities regarding the upgrade
| Quarter<br>_(In which quarter we do upgrade planning)_ | Issue for check upgrades<br>_(Put the link to the issue you plan to use for the upgrade planning)_ | Upgrade execution<br>_(In which quarter we do upgrade execution)_ | Epic for planned upgrade<br>_(Put the link to the epic you plan to use for the upgrade execution)_ | Type of upgrading<br>[`Python`\|`Tool`\|`Libraries`]<br>(What type of object you plan to upgrade) | DRI<br>_(The individual who will check what is required for the upgrade planning)_ |
