Swap latest callouts for fka versionless inline #6607
Merged
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
developer blog
joellabes
commented
Dec 6, 2024
| @@ -84,7 +80,7 @@ All you need to do is configure an environment as staging and enable the **Defer | |||
|
|
|||
| ## Upgrading on a curve | |||
|
|
|||
| Lastly, let’s consider a more specialized use case. Imagine we have a "tiger team" (consisting of a lone analytics engineer named Dave) tasked with upgrading from dbt version 1.6 to the new **Latest release track**, to take advantage of new features and performance improvements. We want to keep the rest of the data team being productive in dbt 1.6 for the time being, while enabling Dave to upgrade and do his work with Latest (and greatest) dbt. | |||
| Lastly, let’s consider a more specialized use case. Imagine we have a "tiger team" (consisting of a lone analytics engineer named Dave) tasked with upgrading from dbt version 1.6 to the new **[Latest release track](/docs/dbt-versions/cloud-release-tracks)**, to take advantage of new features and performance improvements. We want to keep the rest of the data team being productive in dbt 1.6 for the time being, while enabling Dave to upgrade and do his work with Latest (and greatest) dbt. | |||
There was a problem hiding this comment.
This article was written during the Keep on Latest Version phase, so it never talked about versionless and explaining that we used to call it versionless was going to mess with the screenshots! So I've just linked to release tracks.
|
|
||
| In order to get this functionality shipped quickly, EQT opened a pull request, Snowflake helped with some problems we had with CI and a member of dbt Labs helped write the tests and merge the code in! | ||
|
|
||
| dbt now features this functionality in dbt 1.8+ and the "Latest" release track in dbt Cloud (dbt overview [here](/docs/dbt-versions/cloud-release-tracks)). | ||
| dbt now features this functionality in dbt 1.8+ and all [Release tracks](/docs/dbt-versions/cloud-release-tracks) in dbt Cloud. |
There was a problem hiding this comment.
Likewise, this feature is old enough that it's in every release track, not just the Latest one, so saying Latest fka Versionless was less accurate.
| @@ -49,7 +45,7 @@ This API is open and if it requires an API key, handle it similarly to managing | |||
| For simplicity’s sake, we will show how to create them using [pre-hooks](/reference/resource-configs/pre-hook-post-hook) in a model configuration yml file: | |||
|
|
|||
|
|
|||
| ``` | |||
| ```yml | |||
There was a problem hiding this comment.
Fixed a couple of markdownlint warnings while I was here
runleonarun
approved these changes
Dec 6, 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?
As discussed in Slack - swap callouts for a more inline explanation of the changes, for blog posts where Versionless isn't the main focus so the rename doesn't matter as much.
Checklist