I noticed something that didn't happen before I upgraded both dbt to 1.8.3 and elementary to 0.15.2. I have the following configuration in the

dbt_project.yml

vars:
  # Let's leave these disabled until we're sure we want to use them
  dbt_constraints_enabled: false
  # we disable the artifacts autoupload localy, they only are uploaded either in CI or in prod jobs
  disable_dbt_artifacts_autoupload: true
  # the following three vars are pertinent only to production runs
  # if by chance you have the need to run them locally use the following command after your dbt invocation
  # edr report
  disable_run_results: "{{ target.role != 'PRODUCTION_STREAM_PROCESSING_ROLE' }}"
  disable_tests_results: "{{ target.role != 'PRODUCTION_STREAM_PROCESSING_ROLE' }}"
  disable_dbt_invocation_autoupload: "{{ target.role != 'PRODUCTION_STREAM_PROCESSING_ROLE' }}"

I have always understood that the last three variables controlled when to run the hooks and to update the elementary models, and it worked. Now, no matter with what role I execute the statements, the elementary models run