I was trying to test some changes to the dagster-databricks library to contribute a pull request, so I built a wheel from dagster-databricks (pulled from master yesterday, so should be equivalent to 0.16.8 I think?) and installed it in a fresh repo with dagster==1.0.8, and when I tried spinning up a databricks job dagster-databricks tried to install dagster-databricks==1.0.8 on the cluster. I thought I had seen something about that being fixed?

Hey Zach - thanks for the report, there's a fix for this here that we should be able to get out in the release tomorrow: https://github.com/dagster-io/dagster/pull/9696