diff --git a/website/blog/2021-11-23-how-to-upgrade-dbt-versions.md b/website/blog/2021-11-23-how-to-upgrade-dbt-versions.md index 3aa9368a2ca..5098e9d29e3 100644 --- a/website/blog/2021-11-23-how-to-upgrade-dbt-versions.md +++ b/website/blog/2021-11-23-how-to-upgrade-dbt-versions.md @@ -12,6 +12,18 @@ date: 2021-11-29 is_featured: true --- +:::tip February 2024 Update + +It's been a few years since dbt-core turned 1.0! Since then, we've committed to releasing zero breaking changes whenever possible and it's become much easier to upgrade dbt Core versions. + +In 2024, we're taking this promise further by: +- Stabilizing interfaces for everyone — adapter maintainers, metadata consumers, and (of course) people writing dbt code everywhere — as discussed in [our November 2023 roadmap update](https://github.com/dbt-labs/dbt-core/blob/main/docs/roadmap/2023-11-dbt-tng.md). +- Introducing **Keep on latest version** in dbt Cloud. No more manual upgrades and no more need for _a second sandbox project_ just to try out new features in development. For more details, refer to [Upgrade Core version in Cloud](/docs/dbt-versions/upgrade-dbt-version-in-cloud). + +We're leaving the rest of this post as is, so we can all remember how it used to be. Enjoy a stroll down memory lane. + +::: + As we get closer to dbt v1.0 shipping in December, it's a perfect time to get your installation up to scratch. dbt 1.0 represents the culmination of over five years of development and refinement to the analytics engineering experience - smoothing off sharp edges, speeding up workflows and enabling whole new classes of work. Even with all the new shinies on offer, upgrading can be daunting – you rely on dbt to power your analytics workflow and can’t afford to change things just to discover that your daily run doesn’t work anymore. I’ve been there. This is the checklist I wish I had when I owned my last company’s dbt project. diff --git a/website/docs/best-practices/clone-incremental-models.md b/website/docs/best-practices/clone-incremental-models.md index 11075b92161..b3b037847ae 100644 --- a/website/docs/best-practices/clone-incremental-models.md +++ b/website/docs/best-practices/clone-incremental-models.md @@ -7,7 +7,7 @@ hoverSnippet: Learn how to clone incremental models for CI jobs. --- Before you begin, you must be aware of a few conditions: -- `dbt clone` is only available with dbt version 1.6 and newer. Refer to our [upgrade guide](/docs/dbt-versions/upgrade-core-in-cloud) for help enabling newer versions in dbt Cloud +- `dbt clone` is only available with dbt version 1.6 and newer. Refer to our [upgrade guide](/docs/dbt-versions/upgrade-dbt-version-in-cloud) for help enabling newer versions in dbt Cloud - This strategy only works for warehouse that support zero copy cloning (otherwise `dbt clone` will just create pointer views). - Some teams may want to test that their incremental models run in both incremental mode and full-refresh mode. diff --git a/website/docs/best-practices/how-we-mesh/mesh-4-faqs.md b/website/docs/best-practices/how-we-mesh/mesh-4-faqs.md index 2b11c3563eb..2f984da9d04 100644 --- a/website/docs/best-practices/how-we-mesh/mesh-4-faqs.md +++ b/website/docs/best-practices/how-we-mesh/mesh-4-faqs.md @@ -273,7 +273,7 @@ The [dbt Cloud CLI](/docs/cloud/cloud-cli-installation) allows users to develop -Yes, your account must be on [at least dbt v1.6](/docs/dbt-versions/upgrade-core-in-cloud) to take advantage of [cross-project dependencies](/docs/collaborate/govern/project-dependencies), one of the most crucial underlying capabilities required to implement a dbt Mesh. +Yes, your account must be on [at least dbt v1.6](/docs/dbt-versions/upgrade-dbt-version-in-cloud) to take advantage of [cross-project dependencies](/docs/collaborate/govern/project-dependencies), one of the most crucial underlying capabilities required to implement a dbt Mesh. diff --git a/website/docs/docs/build/about-metricflow.md b/website/docs/docs/build/about-metricflow.md index 19d27bc60d2..fc83af63306 100644 --- a/website/docs/docs/build/about-metricflow.md +++ b/website/docs/docs/build/about-metricflow.md @@ -15,7 +15,7 @@ MetricFlow handles SQL query construction and defines the specification for dbt Before you start, consider the following guidelines: - Define metrics in YAML and query them using these [new metric specifications](https://github.com/dbt-labs/dbt-core/discussions/7456). -- You must be on [dbt version](/docs/dbt-versions/upgrade-core-in-cloud) 1.6 or higher to use MetricFlow. +- You must be on [dbt version](/docs/dbt-versions/upgrade-dbt-version-in-cloud) 1.6 or higher to use MetricFlow. - Use MetricFlow with Snowflake, BigQuery, Databricks, Postgres (dbt Core only), or Redshift. - Discover insights and query your metrics using the [dbt Semantic Layer](/docs/use-dbt-semantic-layer/dbt-sl) and its diverse range of [available integrations](/docs/use-dbt-semantic-layer/avail-sl-integrations). diff --git a/website/docs/docs/build/unit-tests.md b/website/docs/docs/build/unit-tests.md index 71c464cbd40..6c83e435290 100644 --- a/website/docs/docs/build/unit-tests.md +++ b/website/docs/docs/build/unit-tests.md @@ -9,9 +9,9 @@ keywords: --- :::note closed beta -Unit testing is currently in closed beta for dbt Cloud accounts that have updated to a [versionless environment](/docs/dbt-versions/upgrade-core-in-cloud). +Support for unit testing dbt models is available to dbt Cloud customers who have chosen to [Keep on latest version](/docs/dbt-versions/upgrade-dbt-version-in-cloud#keep-on-latest-version). This is currently in closed beta, starting with select customers and rolling out to wider availability through February and March. -It is available now as an alpha feature for dbt Core v1.8 users. +For dbt Core, unit tests will be available in v1.8, planned for late April 2024. The v1.8.0-b1 release of `dbt-core` & dbt Labs-maintained adapters is planned for February 28. ::: diff --git a/website/docs/docs/cloud/cloud-cli-installation.md b/website/docs/docs/cloud/cloud-cli-installation.md index e66642067b6..308e879be6e 100644 --- a/website/docs/docs/cloud/cloud-cli-installation.md +++ b/website/docs/docs/cloud/cloud-cli-installation.md @@ -25,7 +25,7 @@ dbt commands are run against dbt Cloud's infrastructure and benefit from: ## Prerequisites The dbt Cloud CLI is available in all [deployment regions](/docs/cloud/about-cloud/access-regions-ip-addresses) and for both multi-tenant and single-tenant accounts (Azure single-tenant not supported at this time). -- Ensure you are using dbt version 1.5 or higher. Refer to [dbt Cloud versions](/docs/dbt-versions/upgrade-core-in-cloud) to upgrade. +- Ensure you are using dbt version 1.5 or higher. Refer to [dbt Cloud versions](/docs/dbt-versions/upgrade-dbt-version-in-cloud) to upgrade. - Note that SSH tunneling for [Postgres and Redshift](/docs/cloud/connect-data-platform/connect-redshift-postgresql-alloydb) connections doesn't support the dbt Cloud CLI yet. ## Install dbt Cloud CLI diff --git a/website/docs/docs/cloud/configure-cloud-cli.md b/website/docs/docs/cloud/configure-cloud-cli.md index 7a673d4a18a..8966080dc0a 100644 --- a/website/docs/docs/cloud/configure-cloud-cli.md +++ b/website/docs/docs/cloud/configure-cloud-cli.md @@ -15,7 +15,7 @@ import CloudCLIFlag from '/snippets/_cloud-cli-flag.md'; - You must set up a project in dbt Cloud. - **Note** — If you're using the dbt Cloud CLI, you can connect to your [data platform](/docs/cloud/connect-data-platform/about-connections) directly in the dbt Cloud interface and don't need a [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file. - You must have your [personal development credentials](/docs/dbt-cloud-environments#set-developer-credentials) set for that project. The dbt Cloud CLI will use these credentials, stored securely in dbt Cloud, to communicate with your data platform. -- You must be on dbt version 1.5 or higher. Refer to [dbt Cloud versions](/docs/dbt-versions/upgrade-core-in-cloud) to upgrade. +- You must be on dbt version 1.5 or higher. Refer to [dbt Cloud versions](/docs/dbt-versions/upgrade-dbt-version-in-cloud) to upgrade. ## Configure the dbt Cloud CLI diff --git a/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md b/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md index 211ce054820..2dcc17e4ee9 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md +++ b/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md @@ -1,5 +1,5 @@ --- -title: "Upgrading to v1.8 (alpha)" +title: "Upgrading to v1.8 (beta)" id: upgrading-to-v1.8 description: New features and changes in dbt Core v1.8 displayed_sidebar: "docs" @@ -9,9 +9,19 @@ displayed_sidebar: "docs" - Changelog (coming soon) - [CLI Installation guide](/docs/core/installation-overview) -- [Cloud upgrade guide](/docs/dbt-versions/upgrade-core-in-cloud) +- [Cloud upgrade guide](/docs/dbt-versions/upgrade-dbt-version-in-cloud) - Release schedule (coming soon) +:::tip Keep on latest version, always + +Starting this year, let dbt Labs handle version upgrades for you. With dbt Cloud, you can get early access to new functionality before it lands in the final release of dbt Core v1.8 and without the need of managing your own version upgrades. For more details, refer to [Upgrade Core version in Cloud](/docs/dbt-versions/upgrade-dbt-version-in-cloud). + +The **Keep on latest version** setting is currently available in beta for select dbt Cloud customers, rolling out to wider availability through February and March. + +For users of dbt Core, the v1.8.0-b1 release of `dbt-core` & dbt Labs-maintained adapters is planned for February 28. + +::: + ## What to know before upgrading dbt Labs is committed to providing backward compatibility for all versions 1.x, with the exception of any changes explicitly mentioned below. If you encounter an error upon upgrading, please let us know by [opening an issue](https://github.com/dbt-labs/dbt-core/issues/new). diff --git a/website/docs/docs/dbt-versions/core-upgrade/02-upgrading-to-v1.7.md b/website/docs/docs/dbt-versions/core-upgrade/02-upgrading-to-v1.7.md index 1f40aaa9f40..1346d610385 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/02-upgrading-to-v1.7.md +++ b/website/docs/docs/dbt-versions/core-upgrade/02-upgrading-to-v1.7.md @@ -9,7 +9,7 @@ displayed_sidebar: "docs" - [Changelog](https://github.com/dbt-labs/dbt-core/blob/8aaed0e29f9560bc53d9d3e88325a9597318e375/CHANGELOG.md) - [CLI Installation guide](/docs/core/installation-overview) -- [Cloud upgrade guide](/docs/dbt-versions/upgrade-core-in-cloud) +- [Cloud upgrade guide](/docs/dbt-versions/upgrade-dbt-version-in-cloud) - [Release schedule](https://github.com/dbt-labs/dbt-core/issues/8260) ## What to know before upgrading diff --git a/website/docs/docs/dbt-versions/core-upgrade/03-upgrading-to-v1.6.md b/website/docs/docs/dbt-versions/core-upgrade/03-upgrading-to-v1.6.md index a70f220edc8..e71fa5eab77 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/03-upgrading-to-v1.6.md +++ b/website/docs/docs/dbt-versions/core-upgrade/03-upgrading-to-v1.6.md @@ -14,7 +14,7 @@ dbt Core v1.6 has three significant areas of focus: - [Changelog](https://github.com/dbt-labs/dbt-core/blob/1.6.latest/CHANGELOG.md) - [dbt Core installation guide](/docs/core/installation-overview) -- [Cloud upgrade guide](/docs/dbt-versions/upgrade-core-in-cloud) +- [Cloud upgrade guide](/docs/dbt-versions/upgrade-dbt-version-in-cloud) - [Release schedule](https://github.com/dbt-labs/dbt-core/issues/7481) ## What to know before upgrading diff --git a/website/docs/docs/dbt-versions/core-upgrade/05-upgrading-to-v1.5.md b/website/docs/docs/dbt-versions/core-upgrade/05-upgrading-to-v1.5.md index 7e696e0ba3c..abd3819f9dd 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/05-upgrading-to-v1.5.md +++ b/website/docs/docs/dbt-versions/core-upgrade/05-upgrading-to-v1.5.md @@ -13,7 +13,7 @@ dbt Core v1.5 is a feature release, with two significant additions: - [Changelog](https://github.com/dbt-labs/dbt-core/blob/1.5.latest/CHANGELOG.md) - [CLI Installation guide](/docs/core/installation-overview) -- [Cloud upgrade guide](/docs/dbt-versions/upgrade-core-in-cloud) +- [Cloud upgrade guide](/docs/dbt-versions/upgrade-dbt-version-in-cloud) - [Release schedule](https://github.com/dbt-labs/dbt-core/issues/6715) ## What to know before upgrading diff --git a/website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.4.md b/website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.4.md index 41e19956690..fa37075c727 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.4.md +++ b/website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.4.md @@ -9,7 +9,7 @@ displayed_sidebar: "docs" - [Changelog](https://github.com/dbt-labs/dbt-core/blob/1.4.latest/CHANGELOG.md) - [CLI Installation guide](/docs/core/installation-overview) -- [Cloud upgrade guide](/docs/dbt-versions/upgrade-core-in-cloud) +- [Cloud upgrade guide](/docs/dbt-versions/upgrade-dbt-version-in-cloud) **Final release:** January 25, 2023 diff --git a/website/docs/docs/dbt-versions/core-upgrade/07-upgrading-to-v1.3.md b/website/docs/docs/dbt-versions/core-upgrade/07-upgrading-to-v1.3.md index 7febb0bade9..d209e70643c 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/07-upgrading-to-v1.3.md +++ b/website/docs/docs/dbt-versions/core-upgrade/07-upgrading-to-v1.3.md @@ -9,7 +9,7 @@ displayed_sidebar: "docs" - [Changelog](https://github.com/dbt-labs/dbt-core/blob/1.3.latest/CHANGELOG.md) - [CLI Installation guide](/docs/core/installation-overview) -- [Cloud upgrade guide](/docs/dbt-versions/upgrade-core-in-cloud) +- [Cloud upgrade guide](/docs/dbt-versions/upgrade-dbt-version-in-cloud) ## What to know before upgrading diff --git a/website/docs/docs/dbt-versions/core-upgrade/08-upgrading-to-v1.2.md b/website/docs/docs/dbt-versions/core-upgrade/08-upgrading-to-v1.2.md index 17e62c90b43..dd9cb4742ea 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/08-upgrading-to-v1.2.md +++ b/website/docs/docs/dbt-versions/core-upgrade/08-upgrading-to-v1.2.md @@ -9,7 +9,7 @@ displayed_sidebar: "docs" - [Changelog](https://github.com/dbt-labs/dbt-core/blob/1.2.latest/CHANGELOG.md) - [CLI Installation guide](/docs/core/installation-overview) -- [Cloud upgrade guide](/docs/dbt-versions/upgrade-core-in-cloud) +- [Cloud upgrade guide](/docs/dbt-versions/upgrade-dbt-version-in-cloud) ## What to know before upgrading diff --git a/website/docs/docs/dbt-versions/core-upgrade/09-upgrading-to-v1.1.md b/website/docs/docs/dbt-versions/core-upgrade/09-upgrading-to-v1.1.md index aee3413e1ad..7191cb4a915 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/09-upgrading-to-v1.1.md +++ b/website/docs/docs/dbt-versions/core-upgrade/09-upgrading-to-v1.1.md @@ -9,7 +9,7 @@ displayed_sidebar: "docs" - [Changelog](https://github.com/dbt-labs/dbt-core/blob/1.1.latest/CHANGELOG.md) - [CLI Installation guide](/docs/core/installation-overview) -- [Cloud upgrade guide](/docs/dbt-versions/upgrade-core-in-cloud) +- [Cloud upgrade guide](/docs/dbt-versions/upgrade-dbt-version-in-cloud) ## What to know before upgrading diff --git a/website/docs/docs/dbt-versions/core-upgrade/10-upgrading-to-v1.0.md b/website/docs/docs/dbt-versions/core-upgrade/10-upgrading-to-v1.0.md index 9cbfae50831..013d70b311c 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/10-upgrading-to-v1.0.md +++ b/website/docs/docs/dbt-versions/core-upgrade/10-upgrading-to-v1.0.md @@ -11,7 +11,7 @@ displayed_sidebar: "docs" - [Discourse](https://discourse.getdbt.com/t/3180) - [Changelog](https://github.com/dbt-labs/dbt-core/blob/1.0.latest/CHANGELOG.md) - [CLI Installation guide](/docs/core/installation-overview) -- [Cloud upgrade guide](/docs/dbt-versions/upgrade-core-in-cloud) +- [Cloud upgrade guide](/docs/dbt-versions/upgrade-dbt-version-in-cloud) ## What to know before upgrading diff --git a/website/docs/docs/dbt-versions/core-versions.md b/website/docs/docs/dbt-versions/core-versions.md index 3ebf988c136..16759ec740f 100644 --- a/website/docs/docs/dbt-versions/core-versions.md +++ b/website/docs/docs/dbt-versions/core-versions.md @@ -2,12 +2,20 @@ title: "About dbt Core versions" id: "core" description: "Learn about semantic versioning for dbt Core, and how long those versions are supported." -pagination_next: "docs/dbt-versions/upgrade-core-in-cloud" +pagination_next: "docs/dbt-versions/upgrade-dbt-version-in-cloud" pagination_prev: null --- dbt Core releases follow [semantic versioning](https://semver.org/) guidelines. For more on how we use semantic versions, see [How dbt Core uses semantic versioning](#how-dbt-core-uses-semantic-versioning). +:::tip Keep on latest version, always + +_Did you know that you can always be working on the latest version?_ + +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 [Keep on latest version](/docs/dbt-versions/upgrade-dbt-version-in-cloud#keep-on-latest-version) setting for details. + +::: + dbt Labs provides different support levels for different versions, which may include new features, bug fixes, or security patches: @@ -17,7 +25,7 @@ dbt Labs provides different support levels for different versions, which may inc ### Further reading -- To learn how you can use dbt Core versions in dbt Cloud, see [Choosing a dbt Core version](/docs/dbt-versions/upgrade-core-in-cloud). +- To learn how you can use dbt Core versions in dbt Cloud, see [Choosing a dbt Core version](/docs/dbt-versions/upgrade-dbt-version-in-cloud). - To learn about installing dbt Core, see "[How to install dbt Core](/docs/core/installation-overview)." - 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`](/reference/project-configs/require-dbt-version) and [`dbt_version`](/reference/dbt-jinja-functions/dbt_version). @@ -29,7 +37,7 @@ All dbt Core versions released prior to 1.0 and their version-specific documenta 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](/docs/dbt-versions/upgrade-core-in-cloud) or [dbt Core](/docs/core/installation-overview#upgrading-dbt-core) to continue receiving support. +We recommend upgrading to a newer version in [dbt Cloud](/docs/dbt-versions/upgrade-dbt-version-in-cloud) or [dbt Core](/docs/core/installation-overview#upgrading-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. @@ -41,7 +49,7 @@ All dbt Core v1.0 and later are available in dbt Cloud until further notice. In 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](/docs/dbt-versions/upgrade-core-in-cloud). +- You can use it in dbt Cloud. For more on dbt Cloud versioning, see [Choosing a dbt version](/docs/dbt-versions/upgrade-dbt-version-in-cloud). - 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 diff --git a/website/docs/docs/dbt-versions/release-notes/72-Feb-2024/keep-on-latest-version.md b/website/docs/docs/dbt-versions/release-notes/72-Feb-2024/keep-on-latest-version.md new file mode 100644 index 00000000000..188f9f0102a --- /dev/null +++ b/website/docs/docs/dbt-versions/release-notes/72-Feb-2024/keep-on-latest-version.md @@ -0,0 +1,19 @@ +--- +title: "New: Keep on latest version" +description: "February 2024: New setting, called Keep on latest version, that allows dbt Labs to handle version upgrades for you." +sidebar_label: "New: Keep on latest version" +sidebar_position: 06 +tags: [Feb-2024] +date: 2024-02-14 +--- + +# New: Keep on latest version + +_Now available in the dbt version dropdown in dbt Cloud — starting with select customers, rolling out to wider availability through February and March._ + +When the new **Keep on latest version** setting is enabled, you always get the latest fixes and early access to new functionality for your dbt project. dbt Labs will handle upgrades behind-the-scenes, as part of testing and redeploying the dbt Cloud application — just like other dbt Cloud capabilities and other SaaS tools that you're using. No more manual upgrades and no more need for _a second sandbox project_ just to try out new features in development. + +To learn more about the new setting, refer to [Keep on latest version](/docs/dbt-versions/upgrade-dbt-version-in-cloud#keep-on-latest-version) for details. + + + diff --git a/website/docs/docs/dbt-versions/release-notes/72-Feb-2024/override-dbt-version.md b/website/docs/docs/dbt-versions/release-notes/72-Feb-2024/override-dbt-version.md index 389665d8ba8..4c368ab4eb5 100644 --- a/website/docs/docs/dbt-versions/release-notes/72-Feb-2024/override-dbt-version.md +++ b/website/docs/docs/dbt-versions/release-notes/72-Feb-2024/override-dbt-version.md @@ -7,7 +7,7 @@ tags: [Feb-2024] date: 2024-02-02 --- -You can now [override the dbt version](/docs/dbt-versions/upgrade-core-in-cloud#override-dbt-version) that's configured for the development environment within your project and use a different version — affecting only your user account. This lets you test new dbt features without impacting other people working on the same project. And when you're satisfied with the test results, you can safely upgrade the dbt version for your project(s). +You can now [override the dbt version](/docs/dbt-versions/upgrade-dbt-version-in-cloud#override-dbt-version) that's configured for the development environment within your project and use a different version — affecting only your user account. This lets you test new dbt features without impacting other people working on the same project. And when you're satisfied with the test results, you can safely upgrade the dbt version for your project(s). Use the **dbt version** dropdown to specify the version to override with. It's available on your project's credentials page in the **User development settings** section. For example: diff --git a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/legacy-sl.md b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/legacy-sl.md index f6c18b2a053..ae7fa2c1a44 100644 --- a/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/legacy-sl.md +++ b/website/docs/docs/dbt-versions/release-notes/74-Dec-2023/legacy-sl.md @@ -35,5 +35,5 @@ The [re-released dbt Semantic Layer](/docs/use-dbt-semantic-layer/dbt-sl), power - Feedback and community support — Engage and share feedback with the dbt Labs team and dbt Community slack using channels like [#dbt-cloud-semantic-layer](https://getdbt.slack.com/archives/C046L0VTVR6) and [#dbt-metricflow](https://getdbt.slack.com/archives/C02CCBBBR1D). Or reach out to your dbt Cloud account representative. - Resources for upgrading — Refer to some additional info and resources to help you upgrade your dbt version: - - [Upgrade version in dbt Cloud](/docs/dbt-versions/upgrade-core-in-cloud) + - [Upgrade version in dbt Cloud](/docs/dbt-versions/upgrade-dbt-version-in-cloud) - [Version migration guides](/docs/dbt-versions/core-upgrade) diff --git a/website/docs/docs/dbt-versions/release-notes/76-Oct-2023/sl-ga.md b/website/docs/docs/dbt-versions/release-notes/76-Oct-2023/sl-ga.md index 06818042539..e488f77c52e 100644 --- a/website/docs/docs/dbt-versions/release-notes/76-Oct-2023/sl-ga.md +++ b/website/docs/docs/dbt-versions/release-notes/76-Oct-2023/sl-ga.md @@ -8,7 +8,7 @@ tags: [Oct-2023] --- :::important -If you're using the legacy Semantic Layer, we _highly_ recommend you [upgrade your dbt version](/docs/dbt-versions/upgrade-core-in-cloud) to dbt v1.6 or higher and [migrate](/guides/sl-migration) to the latest Semantic Layer. +If you're using the legacy Semantic Layer, we _highly_ recommend you [upgrade your dbt version](/docs/dbt-versions/upgrade-dbt-version-in-cloud) to dbt v1.6 or higher and [migrate](/guides/sl-migration) to the latest Semantic Layer. ::: dbt Labs is thrilled to announce that the [dbt Semantic Layer](/docs/use-dbt-semantic-layer/dbt-sl) is now generally available. It offers consistent data organization, improved governance, reduced costs, enhanced efficiency, and accessible data for better decision-making and collaboration across organizations. diff --git a/website/docs/docs/dbt-versions/release-notes/78-Aug-2023/sl-revamp-beta.md b/website/docs/docs/dbt-versions/release-notes/78-Aug-2023/sl-revamp-beta.md index 112fdfe4db0..599257840bb 100644 --- a/website/docs/docs/dbt-versions/release-notes/78-Aug-2023/sl-revamp-beta.md +++ b/website/docs/docs/dbt-versions/release-notes/78-Aug-2023/sl-revamp-beta.md @@ -8,7 +8,7 @@ sidebar_position: 7 --- :::important -If you're using the legacy Semantic Layer, we _highly_ recommend you [upgrade your dbt version](/docs/dbt-versions/upgrade-core-in-cloud) to dbt v1.6 or higher to use the new dbt Semantic Layer. To migrate to the new Semantic Layer, refer to the dedicated [migration guide](/guides/sl-migration) for more info. +If you're using the legacy Semantic Layer, we _highly_ recommend you [upgrade your dbt version](/docs/dbt-versions/upgrade-dbt-version-in-cloud) to dbt v1.6 or higher to use the new dbt Semantic Layer. To migrate to the new Semantic Layer, refer to the dedicated [migration guide](/guides/sl-migration) for more info. ::: dbt Labs are thrilled to announce the re-release of the [dbt Semantic Layer](/docs/use-dbt-semantic-layer/dbt-sl), now available in [public beta](#public-beta). It aims to bring the best of modeling and semantics to downstream applications by introducing: diff --git a/website/docs/docs/dbt-versions/release-notes/81-May-2023/may-ide-updates.md b/website/docs/docs/dbt-versions/release-notes/81-May-2023/may-ide-updates.md index d85ffa154dd..2f551572c9c 100644 --- a/website/docs/docs/dbt-versions/release-notes/81-May-2023/may-ide-updates.md +++ b/website/docs/docs/dbt-versions/release-notes/81-May-2023/may-ide-updates.md @@ -26,7 +26,7 @@ Stay up-to-date with [IDE-related changes](/tags/ide). - Performance-related upgrades: - Reduced cold start time by 60+% - Improved render time of modals in the IDE by 98% - - Improved IDE performance with dbt Core v1.5+ (faster and snappier – highly encourage you to [upgrade your dbt version](/docs/dbt-versions/upgrade-core-in-cloud)!) + - Improved IDE performance with dbt Core v1.5+ (faster and snappier – highly encourage you to [upgrade your dbt version](/docs/dbt-versions/upgrade-dbt-version-in-cloud)!) - Upgraded sqlfmt (which powers the Format button) to 0.18.0 - Updated Build button to change menu options based on file/model type (snapshot, macro, etc.) - Display message to disable adblocker for file contents error diff --git a/website/docs/docs/dbt-versions/release-notes/83-Mar-2023/1.0-deprecation.md b/website/docs/docs/dbt-versions/release-notes/83-Mar-2023/1.0-deprecation.md index 6b6f646e40e..f157ac07611 100644 --- a/website/docs/docs/dbt-versions/release-notes/83-Mar-2023/1.0-deprecation.md +++ b/website/docs/docs/dbt-versions/release-notes/83-Mar-2023/1.0-deprecation.md @@ -16,6 +16,6 @@ For more info on dbt versions, releases, and dbt Cloud support timeline, refer t Refer to some additional info and resources to help you upgrade your dbt version: - [How to upgrade dbt without fear](https://docs.getdbt.com/blog/upgrade-dbt-without-fear) -- [Upgrade Q&A on breaking changes](/docs/dbt-versions/upgrade-core-in-cloud#upgrading-legacy-versions-under-10) +- [Upgrade Q&A on breaking changes](/docs/dbt-versions/upgrade-dbt-version-in-cloud#upgrading-legacy-versions-under-10) - [Version migration guides](/docs/dbt-versions/core-upgrade) diff --git a/website/docs/docs/dbt-versions/upgrade-core-in-cloud.md b/website/docs/docs/dbt-versions/upgrade-dbt-version-in-cloud.md similarity index 83% rename from website/docs/docs/dbt-versions/upgrade-core-in-cloud.md rename to website/docs/docs/dbt-versions/upgrade-dbt-version-in-cloud.md index 0fc4585be34..2f4044b58f4 100644 --- a/website/docs/docs/dbt-versions/upgrade-core-in-cloud.md +++ b/website/docs/docs/dbt-versions/upgrade-dbt-version-in-cloud.md @@ -1,17 +1,28 @@ --- -title: "Upgrade Core version in Cloud" -id: "upgrade-core-in-cloud" +title: "Upgrade dbt version in Cloud" +id: "upgrade-dbt-version-in-cloud" --- In dbt Cloud, both [jobs](/docs/deploy/jobs) and [environments](/docs/dbt-cloud-environments) are configured to use a specific version of dbt Core. The version can be upgraded at any time. ## Environments -Navigate to the settings page of an environment, then click **edit**. Click the **dbt Version** dropdown bar and make your selection. From this list, you can select an available version of Core to associate with this environment. +Navigate to the settings page of an environment, then click **Edit**. Click the **dbt version** dropdown bar and make your selection. You can select a previous release of dbt Core or [Keep on latest version](#keep-on-latest-version). Be sure to save your changes before navigating away. - + + +### Keep on latest version + +By choosing to **Keep on latest version**, you always get the latest fixes and early access to new functionality for your dbt project. dbt Labs will handle upgrades for you, as part of testing and redeploying the dbt Cloud SaaS application. + +You can upgrade to **Keep on latest version** no matter which version of dbt you currently have selected. As a best practice, dbt Labs recommends that you test the upgrade in development first; use the [Override dbt version](#override-dbt-version) setting to test _your_ project on the latest dbt version before upgrading your deployment environments and the default development environment for all your colleagues. + +:::tip Interested? Let us know! + +This feature is available in beta for select customers, rolling out to wider availability through February and March. If you're interested in early access, please contact your account team to join! + +::: -Be sure to save your changes before navigating away. ### Override dbt version @@ -68,13 +79,13 @@ For more on version support and future releases, see [Understanding dbt Core ver #### Need help upgrading? -If you want more advice on how to upgrade your dbt projects, check out our [migration guides](/docs/dbt-versions/core-upgrade/) and our [upgrading Q&A page](/docs/dbt-versions/upgrade-core-in-cloud#upgrading-legacy-versions-under-10). +If you want more advice on how to upgrade your dbt projects, check out our [migration guides](/docs/dbt-versions/core-upgrade/) and our [upgrading Q&A page](/docs/dbt-versions/upgrade-dbt-version-in-cloud#upgrading-legacy-versions-under-10). ## Upgrading legacy versions under 1.0 -You can use the following sections to successfully upgrade your version of dbt Core in dbt Cloud. We recommend everyone upgrade to the most recent version of dbt Core, as new versions contain enhancements, bug fixes, and updated security features. We document which [versions of dbt Core are currently supported](/docs/dbt-versions/upgrade-core-in-cloud#supported-versions). +You can use the following sections to successfully upgrade your version of dbt Core in dbt Cloud. We recommend everyone upgrade to the most recent version of dbt Core, as new versions contain enhancements, bug fixes, and updated security features. We document which [versions of dbt Core are currently supported](/docs/dbt-versions/upgrade-dbt-version-in-cloud#supported-versions). -There aren't many breaking changes between minor versions, and it may be the case that you don't need to change any code to upgrade to a newer version of dbt in dbt Cloud. There are only breaking changes between minor versions of dbt before dbt 1.0. Minor releases starting with dbt 1.0, do not have breaking code changes. If there are no code changes needed, all you have to do is [change the settings](/docs/dbt-versions/upgrade-core-in-cloud#upgrading-to-the-latest-version-of-dbt-in-cloud) in your environment or job to run a more recent version of dbt. +There aren't many breaking changes between minor versions, and it may be the case that you don't need to change any code to upgrade to a newer version of dbt in dbt Cloud. There are only breaking changes between minor versions of dbt before dbt 1.0. Minor releases starting with dbt 1.0, do not have breaking code changes. If there are no code changes needed, all you have to do is [change the settings](/docs/dbt-versions/upgrade-dbt-version-in-cloud#upgrading-to-the-latest-version-of-dbt-in-cloud) in your environment or job to run a more recent version of dbt. #### Changes between minor versions of dbt that will affect your project @@ -290,7 +301,7 @@ If you believe your project might be affected, read more details in the migratio #### Testing your changes before upgrading -Once you know what code changes you'll need to make, you can start implementing them. We recommend you create a separate dbt project, **Upgrade Project**, to test your changes before making them live in your main dbt project. In your **Upgrade Project**, connect to the same repository you use for your production project. This time, set the development environment [settings](/docs/dbt-versions/upgrade-core-in-cloud) to run the latest version of dbt Core. Next, check out a branch `dbt-version-upgrade`, make the appropriate updates to your project, and verify your dbt project compiles and runs with the new version in the IDE. If upgrading directly to the latest version results in too many issues, try testing your project iteratively on successive minor versions. There are years of development and a few breaking changes between distant versions of dbt Core (for example, 0.14 --> 1.0). The likelihood of experiencing problems upgrading between successive minor versions is much lower, which is why upgrading regularly is recommended. +Once you know what code changes you'll need to make, you can start implementing them. We recommend you create a separate dbt project, **Upgrade Project**, to test your changes before making them live in your main dbt project. In your **Upgrade Project**, connect to the same repository you use for your production project. This time, set the development environment [settings](/docs/dbt-versions/upgrade-dbt-version-in-cloud) to run the latest version of dbt Core. Next, check out a branch `dbt-version-upgrade`, make the appropriate updates to your project, and verify your dbt project compiles and runs with the new version in the IDE. If upgrading directly to the latest version results in too many issues, try testing your project iteratively on successive minor versions. There are years of development and a few breaking changes between distant versions of dbt Core (for example, 0.14 --> 1.0). The likelihood of experiencing problems upgrading between successive minor versions is much lower, which is why upgrading regularly is recommended. Once you have your project compiling and running on the latest version of dbt in the development environment for your `dbt-version-upgrade` branch, try replicating one of your production jobs to run off your branch's code. You can do this by creating a new deployment environment for testing, setting the custom branch to 'ON' and referencing your `dbt-version-upgrade` branch. You'll also need to set the dbt version in this environment to the latest dbt Core version. diff --git a/website/docs/docs/deploy/retry-jobs.md b/website/docs/docs/deploy/retry-jobs.md index beefb35379e..f439351aec5 100644 --- a/website/docs/docs/deploy/retry-jobs.md +++ b/website/docs/docs/deploy/retry-jobs.md @@ -9,7 +9,7 @@ If your dbt job run completed with a status of **Error**, you can rerun it from ## Prerequisites - You have a [dbt Cloud account](https://www.getdbt.com/signup). -- You must be using [dbt version](/docs/dbt-versions/upgrade-core-in-cloud) 1.6 or newer. +- You must be using [dbt version](/docs/dbt-versions/upgrade-dbt-version-in-cloud) 1.6 or newer. - The most recent run of the job hasn't completed successfully. The latest status of the run is **Error**. - The job command that failed in the run must be one that supports the [retry command](/reference/commands/retry). diff --git a/website/docs/docs/use-dbt-semantic-layer/exports.md b/website/docs/docs/use-dbt-semantic-layer/exports.md index eaf5db16439..5b33e825549 100644 --- a/website/docs/docs/use-dbt-semantic-layer/exports.md +++ b/website/docs/docs/use-dbt-semantic-layer/exports.md @@ -18,7 +18,7 @@ Essentially, exports are like any other table in your data platform. They enable ## Prerequisites - You have a multi-tenant dbt Cloud account on a [Team or Enterprise](https://www.getdbt.com/pricing/) plan. (Single-tenant is not supported at this time) -- You are on [dbt version](/docs/dbt-versions/upgrade-core-in-cloud) 1.7 or newer. +- You are on [dbt version](/docs/dbt-versions/upgrade-dbt-version-in-cloud) 1.7 or newer. - You have the dbt Semantic Layer [configured](/docs/use-dbt-semantic-layer/setup-sl) in your dbt project. - You have a dbt Cloud environment with a [Job scheduler](/docs/deploy/job-scheduler) enabled. diff --git a/website/docs/reference/commands/deps.md b/website/docs/reference/commands/deps.md index 900e4ae0041..980386b1c1d 100644 --- a/website/docs/reference/commands/deps.md +++ b/website/docs/reference/commands/deps.md @@ -60,26 +60,34 @@ Update your versions in packages.yml, then run dbt deps -dbt generates the `package-lock.yml` file in the _project_root_ where `packages.yml` is recorded, which contains all the resolved packages, the first time you run `dbt deps`. Each subsequent run records the packages installed in this file. If the subsequent `dbt deps` runs contain no updated packages in `dependencies.yml` or `packages.yml`, dbt-core installs from `package-lock.yml`. +## Predictable package installs -When you update the package spec and run `dbt deps` again, the `package-lock.yml` and `packages.yml` files update accordingly. +Starting in dbt Core v1.7, dbt generates a `package-lock.yml` file in the root of your project. This contains the complete set of resolved packages based on the `packages` configuration in `dependencies.yml` or `packages.yml`. Each subsequent invocation of `dbt deps` will install from the _locked_ set of packages specified in this file. Storing the complete set of required packages (with pinned versions) in version-controlled code ensures predictable installs in production and consistency across all developers and environments. -There are two flags related to `package-lock.yml`: -- `dbt deps --lock` — creates or updates the `package-lock.yml` file but does not install the packages. -- `dbt deps --upgrade` — creates or updates the `package-lock.yml` file with the most recent dependencies from `packages.yml`. Also install the packages unless the `--lock` flag is also passed. +The `package-lock.yml` file includes a `sha1_hash` of the `packages` config. This enables dbt to detect if the `packages` config has been updated, and to rerun dependency resolution. To only check for changes to the `packages` config and update the lock file accordingly without installing those packages, provide the `--lock` flag (that is, `dbt deps --lock`). + +It's possible to force package resolution to rerun, even if the `packages` config hasn't changed, by running `dbt deps --upgrade`. This enables you to get the latest commits from the `main` branch of an internally maintained `git` package while accepting the risk of unpredictable builds. An alternative to running `dbt deps --upgrade` in production is to "ignore" the lock file by adding `package-lock.yml` to your project's `.gitignore` file. If you pursue either approach, dbt Labs strongly recommends adding version pins for third-party packages within your `packages` config. + +## Add specific packages + +The `dbt deps` command can add or update an existing package configuration — no need to remember the exact syntax for package configurations. + +For Hub packages (default), which are the easiest to install: -Examples of the `--add-package` flag: ```shell -# add package from hub (--source arg defaults to "hub") dbt deps --add-package dbt-labs/dbt_utils@1.0.0 -# add package from hub with semantic version range +# with semantic version range dbt deps --add-package dbt-labs/snowplow@">=0.7.0,<0.8.0" +``` +For other package types, use the `--source` flag: +```shell # add package from git dbt deps --add-package https://github.com/fivetran/dbt_amplitude@v0.3.0 --source git # add package from local dbt deps --add-package /opt/dbt/redshift --source local ``` + diff --git a/website/docs/reference/commands/version.md b/website/docs/reference/commands/version.md new file mode 100644 index 00000000000..91619f2af7a --- /dev/null +++ b/website/docs/reference/commands/version.md @@ -0,0 +1,31 @@ +--- +title: "About dbt --version" +sidebar_label: "version" +id: "version" +--- + +The `--version` command-line flag returns information about the currently installed version of dbt Core or the dbt Cloud CLI. + +This flag is not supported when invoking dbt in other dbt Cloud runtimes (for example, the IDE or scheduled runs). + + + +```text +$ dbt --version +Core: + - installed: 1.7.6 + - latest: 1.7.6 - Up to date! +Plugins: + - snowflake: 1.7.1 - Up to date! +``` + + + + + +```text +$ dbt --version +dbt Cloud CLI - 0.35.7 (fae78a6f5f6f2d7dff3cab3305fe7f99bd2a36f3 2024-01-18T22:34:52Z) +``` + + diff --git a/website/docs/reference/dbt-commands.md b/website/docs/reference/dbt-commands.md index 2e534049dce..4c4c142ee0d 100644 --- a/website/docs/reference/dbt-commands.md +++ b/website/docs/reference/dbt-commands.md @@ -41,6 +41,7 @@ You can run dbt commands in your specific tool by prefixing them with `dbt`. Fo | [snapshot](/reference/commands/snapshot) | Executes "snapshot" jobs defined in a project | All | All [supported versions](/docs/dbt-versions/core) | | [source](/reference/commands/source) | Provides tools for working with source data (including validating that sources are "fresh") | All | All [supported versions](/docs/dbt-versions/core) | | [test](/reference/commands/test) | Executes tests defined in a project | All | All [supported versions](/docs/dbt-versions/core) | +| [--version](/reference/commands/version) | Displays the currently installed version of dbt CLI | dbt Core
dbt Cloud CLI | All [supported versions](/docs/dbt-versions/core) | diff --git a/website/docs/reference/global-configs/version-compatibility.md b/website/docs/reference/global-configs/version-compatibility.md index c7a1227adaf..fdc9bc1d48e 100644 --- a/website/docs/reference/global-configs/version-compatibility.md +++ b/website/docs/reference/global-configs/version-compatibility.md @@ -12,4 +12,9 @@ You can use the `VERSION_CHECK` config to disable this check and suppress the er dbt --no-version-check run Running with dbt=1.0.0 Found 13 models, 2 tests, 1 archives, 0 analyses, 204 macros, 2 operations.... -``` \ No newline at end of file +``` + +:::info Keep on latest version + + +::: diff --git a/website/docs/reference/project-configs/require-dbt-version.md b/website/docs/reference/project-configs/require-dbt-version.md index 6b17bb46120..1d00eeb0be0 100644 --- a/website/docs/reference/project-configs/require-dbt-version.md +++ b/website/docs/reference/project-configs/require-dbt-version.md @@ -3,6 +3,9 @@ datatype: version-range | [version-range] description: "Read this guide to understand the require-dbt-version configuration in dbt." default_value: None --- + + + ```yml @@ -19,6 +22,12 @@ When you set this configuration, dbt sends a helpful error message for any user If this configuration is not specified, no version check will occur. +:::info Keep on latest version + + + +::: + ### YAML quoting This configuration needs to be interpolated by the YAML parser as a string. As such, you should quote the value of the configuration, taking care to avoid whitespace. For example: @@ -77,6 +86,8 @@ Pinning to a specific dbt version is discouraged because it limits project flexi While you can restrict your project to run only with an exact version of dbt Core, we do not recommend this for dbt Core v1.0.0 and higher. +::: + In the following example, the project will only run with dbt v1.5: diff --git a/website/sidebars.js b/website/sidebars.js index 9c67619bf90..6cb0c656079 100644 --- a/website/sidebars.js +++ b/website/sidebars.js @@ -620,7 +620,7 @@ const sidebarSettings = { link: { type: "doc", id: "docs/dbt-versions/core" }, items: [ "docs/dbt-versions/core", - "docs/dbt-versions/upgrade-core-in-cloud", + "docs/dbt-versions/upgrade-dbt-version-in-cloud", "docs/dbt-versions/product-lifecycles", "docs/dbt-versions/experimental-features", { @@ -918,6 +918,7 @@ const sidebarSettings = { "reference/commands/snapshot", "reference/commands/source", "reference/commands/test", + "reference/commands/version", ], }, { diff --git a/website/snippets/_cloud-environments-info.md b/website/snippets/_cloud-environments-info.md index 2083d8f07ec..929337f86d4 100644 --- a/website/snippets/_cloud-environments-info.md +++ b/website/snippets/_cloud-environments-info.md @@ -29,8 +29,9 @@ Both development and deployment environments have a section called **General Set :::note About dbt version -- dbt Cloud allows users to select any dbt release. At this time, **environments must use a dbt version greater than or equal to v1.0.0;** [lower versions are no longer supported](/docs/dbt-versions/upgrade-core-in-cloud). +- dbt Cloud allows users to select any dbt release. At this time, **environments must use a dbt version greater than or equal to v1.0.0;** [lower versions are no longer supported](/docs/dbt-versions/upgrade-dbt-version-in-cloud). - If you select a current version with `(latest)` in the name, your environment will automatically install the latest stable version of the minor version selected. +- In 2024 we are introducing **Keep on latest version**, which removes the need for manually upgrading environments in the future, while ensuring you get access to the latest fixes and features. This feature is currently in beta for select customers, rolling out to wider availability through February and March._ ::: ### Custom branch behavior diff --git a/website/snippets/_config-dbt-version-check.md b/website/snippets/_config-dbt-version-check.md new file mode 100644 index 00000000000..231143407ce --- /dev/null +++ b/website/snippets/_config-dbt-version-check.md @@ -0,0 +1,23 @@ + +Starting in 2024, when you select **Keep on latest version** in dbt Cloud, dbt will ignore the `require-dbt-version` config. Refer to [Keep on latest version](/docs/dbt-versions/upgrade-dbt-version-in-cloud#keep-on-latest-version) (available in beta) for more details. + +dbt Labs is committed to zero breaking changes for code in dbt projects, with ongoing releases to dbt Cloud and new versions of dbt Core. We also recommend these best practices: + +- **If you install dbt packages** — for use in your project, whether the package is maintained by your colleagues or a member of the open source dbt community, we recommend pinning the package to a specific revision or `version` boundary. Since v1.7, dbt manages this out-of-the-box by _locking_ the version/revision of packages in development in order to guarantee predictable builds in production. To learn more, refer to [Predictable package installs](/reference/commands/deps#predictable-package-installs). +- **If you maintain dbt packages** — whether on behalf of your colleagues or members of the open source community, we recommend writing defensive code that checks to verify that other required packages and global macros are available. For example, if your package depends on the availability of a `date_spine` macro in the global `dbt` namespace, you can write: + + + +```sql +{% macro a_few_days_in_september() %} + + {% if not dbt.get('date_spine') %} + {{ exceptions.raise_compiler_error("Expected to find the dbt.date_spine macro, but it could not be found") }} + {% endif %} + + {{ date_spine("day", "cast('2020-01-01' as date)", "cast('2030-12-31' as date)") }} + +{% endmacro %} +``` + + diff --git a/website/snippets/_new-sl-setup.md b/website/snippets/_new-sl-setup.md index a93f233d09c..e7039c8103a 100644 --- a/website/snippets/_new-sl-setup.md +++ b/website/snippets/_new-sl-setup.md @@ -6,7 +6,7 @@ You can set up the dbt Semantic Layer in dbt Cloud at the environment and projec - You must have a successful run in your new environment. :::tip -If you've configured the legacy Semantic Layer, it has been deprecated. dbt Labs strongly recommends that you [upgrade your dbt version](/docs/dbt-versions/upgrade-core-in-cloud) to dbt version 1.6 or higher to use the latest dbt Semantic Layer. Refer to the dedicated [migration guide](/guides/sl-migration) for details. +If you've configured the legacy Semantic Layer, it has been deprecated. dbt Labs strongly recommends that you [upgrade your dbt version](/docs/dbt-versions/upgrade-dbt-version-in-cloud) to dbt version 1.6 or higher to use the latest dbt Semantic Layer. Refer to the dedicated [migration guide](/guides/sl-migration) for details. ::: 1. In dbt Cloud, create a new [deployment environment](/docs/deploy/deploy-environments#create-a-deployment-environment) or use an existing environment on dbt 1.6 or higher. diff --git a/website/snippets/_sl-deprecation-notice.md b/website/snippets/_sl-deprecation-notice.md index 610b1574b7d..2c42dd199c7 100644 --- a/website/snippets/_sl-deprecation-notice.md +++ b/website/snippets/_sl-deprecation-notice.md @@ -1,5 +1,5 @@ :::info Deprecation of dbt Metrics and the legacy dbt Semantic Layer dbt Labs has deprecated dbt Metrics and the legacy dbt Semantic Layer, both supported on dbt version 1.5 or lower. These changes went into effect on December 15th, 2023. -To migrate and access [MetricFlow](/docs/build/build-metrics-intro) or the re-released dbt Semantic Layer, use the [dbt Semantic Layer migration guide](/guides/sl-migration) and [upgrade your version](/docs/dbt-versions/upgrade-core-in-cloud) in dbt Cloud. +To migrate and access [MetricFlow](/docs/build/build-metrics-intro) or the re-released dbt Semantic Layer, use the [dbt Semantic Layer migration guide](/guides/sl-migration) and [upgrade your version](/docs/dbt-versions/upgrade-dbt-version-in-cloud) in dbt Cloud. ::: diff --git a/website/snippets/_sl-faqs.md b/website/snippets/_sl-faqs.md index 75583bfa2f6..2c1d305b200 100644 --- a/website/snippets/_sl-faqs.md +++ b/website/snippets/_sl-faqs.md @@ -40,7 +40,7 @@ You can use the upcoming feature, Exports, which will allow you to create a [pre -If you're using the legacy Semantic Layer, we highly recommend you [upgrade your dbt version](/docs/dbt-versions/upgrade-core-in-cloud) to dbt v1.6 or higher to use the new dbt Semantic Layer. Refer to the dedicated [migration guide](/guides/sl-migration) for more info. +If you're using the legacy Semantic Layer, we highly recommend you [upgrade your dbt version](/docs/dbt-versions/upgrade-dbt-version-in-cloud) to dbt v1.6 or higher to use the new dbt Semantic Layer. Refer to the dedicated [migration guide](/guides/sl-migration) for more info. diff --git a/website/snippets/_v2-sl-prerequisites.md b/website/snippets/_v2-sl-prerequisites.md index 18f228ad3fe..9c7c86bab6f 100644 --- a/website/snippets/_v2-sl-prerequisites.md +++ b/website/snippets/_v2-sl-prerequisites.md @@ -1,6 +1,6 @@ - Have a dbt Cloud Team or Enterprise account. Suitable for both Multi-tenant and Single-tenant deployment. - Note: Single-tenant accounts should contact their account representative for necessary setup and enablement. -- Have both your production and development environments running [dbt version 1.6 or higher](/docs/dbt-versions/upgrade-core-in-cloud). +- Have both your production and development environments running [dbt version 1.6 or higher](/docs/dbt-versions/upgrade-dbt-version-in-cloud). - Use Snowflake, BigQuery, Databricks, or Redshift. - Create a successful run in the environment where you configure the Semantic Layer. - **Note:** Semantic Layer currently supports the Deployment environment for querying. (_development querying experience coming soon_) diff --git a/website/static/img/docs/dbt-cloud/cloud-configuring-dbt-cloud/choosing-dbt-version/Environment-settings.png b/website/static/img/docs/dbt-cloud/cloud-configuring-dbt-cloud/choosing-dbt-version/Environment-settings.png deleted file mode 100644 index 7484ba94461..00000000000 Binary files a/website/static/img/docs/dbt-cloud/cloud-configuring-dbt-cloud/choosing-dbt-version/Environment-settings.png and /dev/null differ diff --git a/website/static/img/docs/dbt-cloud/cloud-configuring-dbt-cloud/choosing-dbt-version/example-environment-settings.png b/website/static/img/docs/dbt-cloud/cloud-configuring-dbt-cloud/choosing-dbt-version/example-environment-settings.png new file mode 100644 index 00000000000..30711071101 Binary files /dev/null and b/website/static/img/docs/dbt-cloud/cloud-configuring-dbt-cloud/choosing-dbt-version/example-environment-settings.png differ diff --git a/website/vercel.json b/website/vercel.json index a68fb899918..fd58e3f5b82 100644 --- a/website/vercel.json +++ b/website/vercel.json @@ -2,6 +2,11 @@ "cleanUrls": true, "trailingSlash": false, "redirects": [ + { + "source": "/docs/dbt-versions/upgrade-core-in-cloud", + "destination": "/docs/dbt-versions/upgrade-dbt-version-in-cloud", + "permanent": true + }, { "source": "/docs/cloud/about-cloud/regions-ip-addresses", "destination": "/docs/cloud/about-cloud/access-regions-ip-addresses", @@ -1674,7 +1679,7 @@ }, { "source": "/docs/dbt-cloud/cloud-configuring-dbt-cloud/cloud-choosing-a-dbt-version", - "destination": "/docs/dbt-versions/upgrade-core-in-cloud", + "destination": "/docs/dbt-versions/upgrade-dbt-version-in-cloud", "permanent": true }, { @@ -2379,7 +2384,7 @@ }, { "source": "/docs/dbt-cloud/cloud-configuring-dbt-cloud/cloud-upgrading-dbt-versions", - "destination": "/docs/dbt-versions/upgrade-core-in-cloud", + "destination": "/docs/dbt-versions/upgrade-dbt-version-in-cloud", "permanent": true }, { @@ -2854,7 +2859,7 @@ }, { "source": "/docs/dbt-cloud/cloud-configuring-dbt-cloud/cloud-choosing-a-dbt-version", - "destination": "/docs/dbt-versions/upgrade-core-in-cloud", + "destination": "/docs/dbt-versions/upgrade-dbt-version-in-cloud", "permanent": true }, {