Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Mark 1.6 under critical support (#4399)
## What are you changing in this pull request and why? - Changing 1.6 from Active -> Critical support as of 1.7 GA. - This is incorrectly marked as active, hence the change. This is based on the policy from the same page (https://docs.getdbt.com/docs/dbt-versions/core#how-dbt-core-uses-semantic-versioning) : > Newer minor versions transition the previous minor version into "Critical Support" with limited "security" releases for critical security and installation fixes. ## Checklist <!-- Uncomment if you're publishing docs for a prerelease version of dbt (delete if not applicable): - [ ] Add versioning components, as described in [Versioning Docs](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-entire-pages) - [ ] Add a note to the prerelease version [Migration Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/docs/dbt-versions/core-upgrade) --> - [x] Review the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) and [About versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) so my content adheres to these guidelines.
- Loading branch information