Disable UnversionedBreakingChange without setting all other warnings as errors

I’m trying to convert the UnversionedBreakingChange error to a warning in my project.

I tried adding the following config:

      - NoNodesForSelectionCriteria
      - UnversionedBreakingChange

This results in a new error because include: all is required. But if I add include: all it also enables a bunch of other warnings-as-errors that I do not want to enable, such as SeedExceedsLimitSamePath.

Is there a way to tell dbt to treat UnversionedBreakingChange as a warning, not an error, without then enabling all other warnings?

I know that “best practice” is to treat all warnings as errors, but that doesn’t make sense for all projects in all stages of maturity.