A question on code-versioning. I think of dagster as a massively souped up "make" but with some similar concepts of dependency management where makefile targets are data files. In make however, it is very easy to imply dependencies on code (as well as on other data (software defined) assets. Just put the code-file into the dependency. Besides an argument to the asset decorator to bump up versions, is there a more systematic way to do this?

Not quite the same as make, but this can address the use case, I think: https://docs.dagster.io/concepts/assets/software-defined-assets#asset-code-versions