Skip to main content

dbt Version End-of-Life and Deprecation

Urgent Action Required

If you are using dbt versions below 1.7, you must migrate to the default dbt version to ensure continued service and security.

Overview​

As part of our regular updates, we are deprecating older dbt versions that have reached end-of-life (EOL) in dbt's official support lifecycle. This page provides information about the deprecation, why it's necessary, and how to migrate to supported versions.

What's Happening​

We will be deprecating all dbt versions below 1.7 in MATE. If your account is currently using any of these EOL versions, you must take action to migrate to a supported version.

Why This Change is Necessary​

Legacy dbt versions that have reached end-of-life present several critical issues:

Security Risks​

  • No security updates: EOL versions no longer receive security patches from dbt Labs, potentially exposing your data pipelines to security vulnerabilities
  • Compliance concerns: Using unsupported software may conflict with security and compliance requirements

Limited Support and Reliability​

  • No bug fixes: Issues discovered in EOL versions will not be addressed by dbt Labs
  • Missing features: Newer versions offer improved performance, enhanced features, and better functionality
  • Incompatibility: EOL versions may become incompatible with newer Snowflake features or other components

Alignment with Industry Standards​

  • dbt's official support lifecycle: This change aligns with dbt Labs' official support and maintenance policies
  • Best practices: Using supported versions is a fundamental best practice in DataOps

Affected Versions​

The following dbt versions are being deprecated:

  • dbt 1.6 and earlier
  • All versions below 1.7

For information about currently supported dbt versions, see dbt Version Switching.

Action Required​

To continue using MATE services without interruption, you must migrate to the default dbt version.

Migration Steps​

Follow these steps to migrate from a deprecated dbt version:

  1. Identify your current configuration

    Check if you have set a specific dbt version in either:

    • Your variables.yml file, OR
    • Your MATE job definition

  2. Remove the version specification

    Remove or comment out the DATAOPS_FEATURE_MATE_DBT_VERSION variable from your configuration:

    In variables.yml:

    variables.yml
    # Remove or comment out this line:
    # DATAOPS_FEATURE_MATE_DBT_VERSION: "1.5"

    In MATE job definition:

    MATE job YAML
    your_mate_job:
      extends:
        - .modelling_and_transformation_base
      variables:
        # Remove or comment out this line:
        # DATAOPS_FEATURE_MATE_DBT_VERSION: "1.5"
      script:
        - /dataops

  3. Commit and deploy

    Once you've removed the version specification, commit your changes and run your pipeline. Your project will automatically use the default dbt version.

  4. Test your pipeline

    Verify that your MATE jobs run successfully with the default dbt version.

What Happens After Migration​

Once you remove the DATAOPS_FEATURE_MATE_DBT_VERSION variable:

  • Your project will automatically use the DataOps-recommended default dbt version
  • You'll benefit from our automatic version management (see below)
  • Your pipelines will continue to run without interruption

Benefits of Using Default Versions​

By switching to our default dbt version, you'll benefit from automatic version management:

Automatic Updates​

  • Stay current: We regularly update the default version to keep up with dbt releases
  • No manual intervention: You don't need to manually upgrade versions
  • Latest stable features: Access to the newest stable features and improvements

Enhanced Security​

  • Security patches: Automatic access to the latest security updates
  • Bug fixes: Benefit from ongoing bug fixes and improvements
  • Reduced risk: Lower exposure to security vulnerabilities

Improved Performance​

  • Optimizations: Newer versions include performance optimizations
  • Better resource utilization: Enhanced efficiency in query execution and compilation
  • Advanced features: Access to new dbt and Snowflake capabilities

Timeline​

Action Required Immediately

This is an urgent matter. Please complete the migration as soon as possible to avoid any service disruptions.

Deprecated dbt versions will no longer be supported, and pipelines using these versions may experience issues or failures.

Migration Considerations​

Potential Breaking Changes​

When migrating from older dbt versions, be aware of potential breaking changes:

  • Test your models thoroughly after migration
  • Check for deprecated macros or syntax
  • Review dbt release notes for version-specific changes

Version-Specific Features​

If your project relies on version-specific features or workarounds:

  • Review your code for compatibility with newer dbt versions
  • Update any custom macros that may conflict with newer dbt versions
  • Consult the dbt version release notes for changes

Need Help?​

If you're unable to migrate to a newer version or encounter any issues during the migration process, our support team is here to assist you.

Getting Support​

What to Include in Your Support Request​

When reaching out for help, please provide:

  • Your current dbt version
  • The specific error messages or issues you're experiencing
  • Any custom configurations or dependencies that may be affected
  • A description of any blocking issues preventing migration

We're committed to making this transition as smooth as possible and will work with you to resolve any migration challenges.

Last updated on