Open matthieucan opened 3 months ago
Hello! We haven't made a final decision on how we'll approach this going forward. A couple of options are:
Thanks for your fast answer!
If future versions of the json schemas are backwards-compatible, my issues are pretty much addressed. I certainly intend to migrate to newer releases of dbt, but there's always of course a delay between release and migration/adoption.
That said, ideally the json schemas configured in our build systems and IDEs always matches the version in use - even with backwards-compatibility in mind. To that end, perhaps an easy solution to implement could be to:
1.7
, 1.8
, 1.9
latest
folder, which is a symbolic link towards the most recent version folderThis is quite a standard approach for software releases, as it avoids any duplication, and allows both "getting a specific version" and "always getting the latest version". Any thoughts on this?
Hi, I'd like to use the json schema files for dbt 1.8. In my understanding, they are currently stored as
latest
. But if I uselatest
, it will become incorrect oncelatest
refers to 1.9. Would you be willing to have a copy of the currentlatest
under a1.8
folder, like it's done for previous versions?