Deprecate v1.0 from docs

alex-mirkin · Aug 10, 2023 · 0a203ca · 0a203ca
1 parent 8e0b6b8
commit 0a203ca
Show file tree

Hide file tree

Showing 13 changed files with 3 additions and 109 deletions.
diff --git a/contributing/single-sourcing-content.md b/contributing/single-sourcing-content.md
@@ -90,7 +90,7 @@ This component can be added directly to a markdown file in a similar way as othe
 Both properties can be used together to set a range where the content should show. In the example below, this content will only show if the selected version is between **0.21** and **1.0**:
 
 ```markdown
-<VersionBlock lastVersion="1.0">
+<VersionBlock lastVersion="1.6">
 
 	Versioned content here
 

diff --git a/website/dbt-versions.js b/website/dbt-versions.js
@@ -23,10 +23,6 @@ exports.versions = [
     version: "1.1",
     EOLDate: "2023-04-28",
   },
-  {
-    version: "1.0",
-    EOLDate: "2022-12-03"
-  },
 ]
 
 exports.versionedPages = [

diff --git a/website/docs/docs/build/incremental-models.md b/website/docs/docs/build/incremental-models.md
@@ -79,12 +79,6 @@ A `unique_key` enables updating existing rows instead of just appending new rows
 
 Not specifying a `unique_key` will result in append-only behavior, which means dbt inserts all rows returned by the model's SQL into the preexisting target table without regard for whether the rows represent duplicates.
 
-<VersionBlock lastVersion="1.0">
-
-The optional `unique_key` parameter specifies a field that can uniquely identify each row within your model. You can define `unique_key` in a configuration block at the top of your model. If your model doesn't contain a single field that is unique, but rather a combination of columns, we recommend that you create a single column that can serve as a unique identifier (by concatenating and hashing those columns), and pass it into your model's configuration.
-
-</VersionBlock>
-
 <VersionBlock firstVersion="1.1">
 
 The optional `unique_key` parameter specifies a field (or combination of fields) that define the grain of your model. That is, the field(s) identify a single unique row. You can define `unique_key` in a configuration block at the top of your model, and it can be a single column name or a list of column names.

diff --git a/website/docs/docs/building-a-dbt-project/building-models/python-models.md b/website/docs/docs/building-a-dbt-project/building-models/python-models.md
@@ -19,7 +19,7 @@ Below, you'll see sections entitled "❓ **Our questions**." We are excited to h
 
 dbt Python ("dbt-py") models will help you solve use cases that can't be solved with SQL. You can perform analyses using tools available in the open source Python ecosystem, including state-of-the-art packages for data science and statistics. Before, you would have needed separate infrastructure and orchestration to run Python transformations in production. By defining your Python transformations in dbt, they're just models in your project, with all the same capabilities around testing, documentation, and lineage.
 
-<VersionBlock firstVersion="1.0" lastVersion="1.2">
+<VersionBlock lastVersion="1.2">
 
 Python models are supported in dbt Core 1.3 and above.  Learn more about [upgrading your version in dbt Cloud](https://docs.getdbt.com/docs/dbt-cloud/cloud-configuring-dbt-cloud/cloud-upgrading-dbt-versions) and [upgrading dbt Core versions](https://docs.getdbt.com/docs/core-versions#upgrading-to-new-patch-versions).
 

diff --git a/website/docs/docs/core/connect-data-platform/bigquery-setup.md b/website/docs/docs/core/connect-data-platform/bigquery-setup.md
@@ -317,56 +317,6 @@ my-profile:
 
 </VersionBlock>
 
-<VersionBlock lastVersion="1.0">
-
-BigQuery supports query timeouts. By default, the timeout is set to 300 seconds. If a dbt model takes longer than this timeout to complete, then BigQuery may cancel the query and issue the following error:
-
-```
- Operation did not complete within the designated timeout.
-```
-
-To change this timeout, use the `timeout_seconds` configuration:
-
-<File name='profiles.yml'>
-
-```yaml
-my-profile:
-  target: dev
-  outputs:
-    dev:
-      type: bigquery
-      method: oauth
-      project: abc-123
-      dataset: my_dataset
-      timeout_seconds: 600 # 10 minutes
-```
-
-</File>
-
-The `retries` profile configuration designates the number of times dbt should retry queries that result in unhandled server errors. This configuration is only specified for BigQuery targets. Example:
-
-<File name='profiles.yml'>
-
-```yaml
-# This example target will retry BigQuery queries 5
-# times with a delay. If the query does not succeed
-# after the fifth attempt, then dbt will raise an error
-
-my-profile:
-  target: dev
-  outputs:
-    dev:
-      type: bigquery
-      method: oauth
-      project: abc-123
-      dataset: my_dataset
-      retries: 5
-```
-
-</File>
-
-</VersionBlock>
-
 ### Dataset locations
 
 The location of BigQuery datasets can be configured using the `location` configuration in a BigQuery profile.

diff --git a/website/docs/docs/core/connect-data-platform/spark-setup.md b/website/docs/docs/core/connect-data-platform/spark-setup.md
@@ -207,8 +207,6 @@ your_profile_name:
 
 </VersionBlock>
 
-<VersionBlock firstVersion="1.0">
-
 ## Optional configurations
 
 ### Retries
@@ -227,8 +225,6 @@ connect_retries: 3
 
 </File>
 
-</VersionBlock>
-
 ## Caveats
 
 ### Usage with EMR

diff --git a/website/docs/faqs/Core/install-python-compatibility.md b/website/docs/faqs/Core/install-python-compatibility.md
@@ -23,12 +23,6 @@ The latest version of `dbt-core` is compatible with Python versions 3.7, 3.8, 3.
 
 </VersionBlock>
 
-<VersionBlock lastVersion="1.0">
-
-As of v1.0, `dbt-core` is compatible with Python versions 3.7, 3.8, and 3.9.
-
-</VersionBlock>
-
 Adapter plugins and their dependencies are not always compatible with the latest version of Python. For example, dbt-snowflake v0.19 is not compatible with Python 3.9, but dbt-snowflake versions 0.20+ are.
 
 New dbt minor versions will add support for new Python3 minor versions as soon as all dependencies can support it. In turn, dbt minor versions will drop support for old Python3 minor versions right before they reach [end of life](https://endoflife.date/python).

diff --git a/website/docs/guides/legacy/best-practices.md b/website/docs/guides/legacy/best-practices.md
@@ -159,12 +159,6 @@ dbt test --select result:fail --exclude <example test> --defer --state path/to/p
 
 > Note: If you're using the `--state target/` flag, `result:error` and `result:fail` flags can only be selected concurrently(in the same command) if using the `dbt build` command. `dbt test` will overwrite the `run_results.json` from `dbt run` in a previous command invocation.
 
-<VersionBlock lastVersion="1.0">
-
-Only supported by v1.1 or newer.
-
-</VersionBlock>
-
 <VersionBlock firstVersion="1.1">
 
 Only supported by v1.1 or newer.

diff --git a/website/docs/reference/node-selection/methods.md b/website/docs/reference/node-selection/methods.md
@@ -252,11 +252,6 @@ $ dbt seed --select result:error --state path/to/artifacts # run all seeds that
 ```
 
 ### The "source_status" method
-<VersionBlock lastVersion="1.0">
-
-Supported in v1.1 or newer.
-
-</VersionBlock>
 
 <VersionBlock firstVersion="1.1">
 

diff --git a/website/docs/reference/node-selection/syntax.md b/website/docs/reference/node-selection/syntax.md
@@ -174,12 +174,6 @@ $ dbt run --select result:<status>+ state:modified+ --defer --state ./<dbt-artif
 
 ### Fresh rebuilds
 
-<VersionBlock lastVersion="1.0">
-
-Only supported by v1.1 or newer.
-
-</VersionBlock>
-
 <VersionBlock firstVersion="1.1">
 
 Only supported by v1.1 or newer.
@@ -199,11 +193,6 @@ dbt build --select source_status:fresher+
 For more example commands, refer to [Pro-tips for workflows](/guides/legacy/best-practices.md#pro-tips-for-workflows).
 
 ### The "source_status" status
-<VersionBlock lastVersion="1.0">
-
-Only supported by v1.1 or newer.
-
-</VersionBlock>
 
 <VersionBlock firstVersion="1.1">
 

diff --git a/website/docs/reference/resource-configs/persist_docs.md b/website/docs/reference/resource-configs/persist_docs.md
@@ -151,7 +151,7 @@ Some known issues and limitations:
 
 </VersionBlock>
 
-<VersionBlock firstVersion="1.0" lastVersion="1.1">
+<VersionBlock lastVersion="1.1">
 
 - Column names that must be quoted, such as column names containing special characters, will cause runtime errors if column-level `persist_docs` is enabled. This is fixed in v1.2.
 

diff --git a/website/docs/reference/resource-properties/config.md b/website/docs/reference/resource-properties/config.md
@@ -108,12 +108,6 @@ version: 2
 
 <TabItem value="sources">
 
-<VersionBlock lastVersion="1.0">
-
-We have added support for the `config` property on sources in dbt Core v1.1
-
-</VersionBlock>
-
 <VersionBlock firstVersion="1.1">
 
 <File name='models/<filename>.yml'>

diff --git a/website/docs/reference/source-configs.md b/website/docs/reference/source-configs.md
@@ -71,14 +71,6 @@ Sources can be configured via a `config:` block within their `.yml` definitions,
 
 </VersionBlock>
 
-<VersionBlock lastVersion="1.0">
-
-Sources can be configured from the `dbt_project.yml` file under the `sources:` key. This configuration is most useful for configuring sources imported from [a package](package-management). You can disable sources imported from a package to prevent them from rendering in the documentation, or to prevent [source freshness checks](/docs/build/sources#snapshotting-source-data-freshness) from running on source tables imported from packages.
-
-Unlike other resource types, sources do not yet support a `config` property. It is not possible to (re)define source configs hierarchically across multiple YAML files.
-
-</VersionBlock>
-
 ### Examples
 #### Disable all sources imported from a package
 To apply a configuration to all sources included from a [package](/docs/build/packages),