About dbt Core versions

dbt Core releases follow semantic versioning guidelines. For more on how we use semantic versions, see How dbt Core uses semantic versioning.

Go versionless and stay up to date, always

Did you know that you can always be working with the latest features and functionality?

With dbt Cloud, you can get early access to new functionality before it becomes available in dbt Core and without the need of managing your own version upgrades. Refer to the Versionless setting for details.

dbt Labs provides different support levels for different versions, which may include new features, bug fixes, or security patches:

• Active — We will patch regressions, new bugs, and include fixes for older bugs / quality-of-life improvements. We implement these changes when we have high confidence that they're narrowly scoped and won't cause unintended side effects.
• Critical — Newer minor versions transition the previous minor version into "Critical Support" with limited "security" releases for critical security and installation fixes.
• End of Life — Minor versions that have reached EOL no longer receive new patch releases.
• Deprecated — dbt Core versions older than v1.0 are no longer maintained by dbt Labs, nor supported in dbt Cloud.

Latest releases

dbt Core	Initial release	Support level and end date
v1.8	May 9 2024	Active Support — May 8, 2025
v1.7	Nov 2, 2023	dbt Core and dbt Cloud Developer & Team customers: End of Life dbt Cloud Enterprise customers: Critical Support until further notice 1
v1.6	Jul 31, 2023	End of Life ⚠️
v1.5	Apr 27, 2023	End of Life ⚠️
v1.4	Jan 25, 2023	End of Life ⚠️
v1.3	Oct 12, 2022	End of Life ⚠️
v1.2	Jul 26, 2022	End of Life ⚠️
v1.1	Apr 28, 2022	End of Life ⚠️
v1.0	Dec 3, 2021	End of Life ⚠️
v0.X ⛔️	(Various dates)	Deprecated ⛔️

All functionality in dbt Core since the v1.7 release is available in dbt Cloud, early and continuously, by selecting "Versionless".

¹ "Versionless" is now required for the Developer and Teams plans on dbt Cloud. Accounts using older dbt versions will be migrated to "Versionless."

For customers of dbt Cloud Enterprise, dbt v1.7 will continue to be available as an option while dbt Labs rolls out a mechanism for "extended" upgrades. In the meantime, dbt Labs strongly recommends migrating any environments that are still running on older unsupported versions to "Versionless" dbt or dbt v1.7.

Further reading

• To learn how you can use dbt Core versions in dbt Cloud, see Choosing a dbt Core version.
• To learn about installing dbt Core, see "How to install dbt Core."
• To restrict your project to only work with a range of dbt Core versions, or use the currently running dbt Core version, see require-dbt-version and dbt_version.

Version support prior to v1.0

All dbt Core versions released prior to 1.0 and their version-specific documentation have been deprecated. If upgrading to a currently supported version, reference our best practices for upgrading

EOL version support

All dbt Core minor versions that have reached end-of-life (EOL) will have no new patch releases. This means they will no longer receive any fixes, including for known bugs that have been identified. Fixes for those bugs will instead be made in newer minor versions that are still under active support.

We recommend upgrading to a newer version in dbt Cloud or dbt Core to continue receiving support.

All dbt Core v1.0 and later are available in dbt Cloud until further notice. In the future, we intend to align dbt Cloud availability with dbt Core ongoing support. You will receive plenty of advance notice before any changes take place.

Current version support

Minor versions

Minor versions include new features and capabilities. They will be supported for one year from their initial release date. dbt Labs is committed to this 12-month support timeframe. Our mechanism for continuing to support a minor version is by releasing new patches: small, targeted bug fixes. Whenever we refer to a minor version, such as v1.0, we always mean its latest available patch release (v1.0.x).

While a minor version is officially supported:

• You can use it in dbt Cloud. For more on dbt Cloud versioning, see Choosing a dbt version.
• You can select it from the version dropdown on this website, to see documentation that is accurate for use with that minor version.

Ongoing patches

During the 12-month support window, we will continue to release new patch versions that include fixes.

Active Support: In the first few months after a minor version's initial release, we will patch it with "bugfix" releases. These will include fixes for regressions and net-new bugs that were present in the minor version's original release.

Critical Support: When a newer minor version is available, we will transition the previous minor version into "Critical Support." Subsequent patches to that older minor version will be "security" releases only, limited to critical fixes related to security and installation.

After a minor version reaches the end of its critical support period, one year after its initial release, no new patches will be released.

Future versions

For the latest information about upcoming releases, including planned release dates and which features and fixes might be included, consult the dbt-core repository milestones and product roadmaps.

Best practices for upgrading

Because of our new version practice, we've outlined best practices and expectations for dbt users to upgrade as we continue to release new versions of dbt Core.

Upgrading to new patch versions

We expect users to upgrade to patches as soon as they're available. When we refer to a "minor version" of dbt Core, such as v1.0, we are always referring to the latest available patch release for that minor version. We encourage you to structure your development and production environments so that you can always install the latest patches of dbt-core and any adapter plugins. (Note that patch numbers may be different between dbt-core and plugins. See below for an explanation.)

Upgrading to new minor versions

During the official support period, minor versions will remain available in dbt Cloud and the version dropdown on the docs site. While we do not expect users to immediately upgrade to newer minor versions as soon as they're available, there will always be some features and fixes only available for users of the latest minor version.

Trying prereleases

All dbt Core versions are available as prereleases before the final release. "Release candidates" are available for testing, in production-like environments, two weeks before the final release. For minor versions, we also aim to release one or more "betas," which include new features and invite community feedback, 4+ weeks before the final release. It is in your interest to help us test prereleases—we need your help!

How dbt Core uses semantic versioning

Like many software projects, dbt Core releases follow semantic versioning, which defines three types of version releases.

• Major versions: To date, dbt Core has had one major version release: v1.0.0. When v2.0.0 is released, it will introduce new features, and functionality that has been announced for deprecation will stop working.
• Minor versions, also called "feature" releases, include a mix of new features, behind-the-scenes improvements, and changes to existing capabilities that are backwards compatible with previous minor versions. They will not break code in your project that relies on documented functionality.
• Patch versions, also called "bugfix" or "security" releases, include fixes only. These fixes could be needed to restore previous (documented) behavior, fix obvious shortcomings of new features, or offer critical fixes for security or installation issues. We are judicious about which fixes are included in patch releases, to minimize the surface area of changes.

We are committed to avoiding breaking changes in minor versions for end users of dbt. There are two types of breaking changes that may be included in minor versions:

• Changes to the Python interface for adapter plugins. These changes are relevant only to adapter maintainers, and they will be clearly communicated in documentation and release notes. For more information, refer to Build, test, document, and promote adapters guide.
• Changes to metadata interfaces, including artifacts and logging, signalled by a version bump. Those version upgrades may require you to update external code that depends on these interfaces, or to coordinate upgrades between dbt orchestrations that share metadata, such as state-powered selection.

How we version adapter plugins

When you use dbt, you use a combination of dbt-core and an adapter plugin specific to your database. You can see the current list in Supported Data Platforms. Both dbt-core and dbt adapter plugins follow semantic versioning.

dbt-core and adapter plugins use the dbt-adapters interface to coordinate new features and behind-the-scenes changes. New adapter features are defined in dbt-adapters (which dbt-core will use). These features are opt-in, meaning they only impact adapters that explicitly implement them. This allows us to independently release adapters, dbt-adapters, and dbt-core without creating a broken experience for users.

Unlike dbt-core versions before 1.8, the minor and patch version numbers might not match between dbt-core and the adapter plugin(s) you've installed.

For example, you might find you're using dbt-core==1.8.0 with dbt-snowflake==1.9.0. Even though these don't have the same minor version, they can still work together as they both work with dbt-adapters==1.8.0. Patch releases can contain important bug or security fixes so it’s critical to stay up to date.

You can use the dbt --version command to see which versions you have installed:

$ dbt --version
Core:
  - installed: 1.8.0
  - latest:    1.8.0 - Up to date!

Plugins:
  - snowflake: 1.9.0 - Up to date!

You can see which version of the registered adapter that's being invoked in the logs. Below is an example of the message in the logs/dbt.log file:

[0m13:13:48.572182 [info ] [MainThread]: Registered adapter: snowflake=1.9.0

It's likely that newer patches have become available since then, so it's always important to check and make sure you're up to date!