Remove v1.6 from docs #6375
Merged
Remove v1.6 from docs #6375
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
content
matthewshaver
changed the title
runleonarun
reviewed
Oct 28, 2024
There was a problem hiding this comment.
I saw a few 1.6 references that might be worth removing:
- https://docs-getdbt-com-git-eol-dbt-labs.vercel.app/docs/collaborate/govern/model-versions#why-version-a-model Paragraph beginning with "dbt Core 1.6 introduced"
- https://docs-getdbt-com-git-eol-dbt-labs.vercel.app/best-practices/clone-incremental-models
- https://docs-getdbt-com-git-eol-dbt-labs.vercel.app/docs/collaborate/govern/project-dependencies#prerequisites (maybe just supported version of dbt" is good enough here)
Otherwise it looks good!
website/docs/docs/build/packages.md
Outdated
| @@ -83,12 +83,8 @@ packages: | |||
| version: [">=0.7.0", "<0.8.0"] | |||
| ``` | |||
|
|
|||
| <VersionBlock firstVersion="1.7"> | |||
|
|
|||
| Beginning in v1.7, `dbt deps` "pins" each package by default. See ["Pinning packages"](#pinning-packages) for details. | |||
There was a problem hiding this comment.
At what point would we get rid of "Beginning in v1.7?" Once 1.7 is no longer supported?
matthewshaver
commented
Oct 29, 2024
Thanks @runleonarun Anywhere it's indicating a prerequisite, I left it in. I did update some of the language to be consistent elsewhere. I left it in the Model Version doc because it tells a story about when we created it and why we used the feature. |
runleonarun
approved these changes
Oct 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What are you changing in this pull request and why?
Removes v1.6 from the dropdown.
Removes content where v1.6 was "lastversion"
Cleans up "firstversion="1.7" blocks
Removes appropriate page version blocks
Checklist
🚀 Deployment available! Here are the direct links to the updated files: