Oh, maybe I should prioritize next always setting ...
# development
h
Oh, maybe I should prioritize next always setting a default resolve? The only other followups we had for this line of work is: • update
check
to run on all relevant resolves for the root, whereas now we choose one. Imo lets punt • maybe eagerly error if you explicitly depend on a
jvm_artifact
from an incompatible resolve? And then staleness checks are still missing