Using local copies of artifact schemas for validation causes breakage

[psygnoser]

Recently the package dbt-common, which is an dependency of dbt-core has updated from 1.5.0 to 1.6.0. This introduced schema changes in mainfest.json which in turn caused this package to break, since it's using a local copy of the V12 schema which has meanwhile updated to include the new schema changes (see here).

At first I've actually opened an issue with them (please see here ), but apparently their policy is, that changes to the schemas are allowed to happen in between versions, which means your package might fail at any time (when any dbt-core dependancies update etc), even if no new artifact schema version was released.

[jochemvandooren]

Just wanted to say that I also have this problem. I am unable to use this package anymore because of the changes mentioned.

[psygnoser]

@jochemvandooren The workaround is to lock dbt-common to version 1.5.0.

[jochemvandooren]

@jochemvandooren The workaround is to lock dbt-common to version 1.5.0.

Yes, sorry I managed fix it indeed 👍 . Not the desired solution though!