Job resolution failures with relative paths in 1.13.0

[robcresswell]

I'm confused as to how this can happen, but 1.12.0 works fine for me locally, but 1.13.0 fails to resolve any job paths. Is there something in the release pipeline releasing the wrong version or something? All the resolution changes looked like 1.11.0 / 1.12.0

[GiovaniGuizzo]

Shouldn't be happening. If you look at the commit history, we haven't touched job resolution in 1.13.0. Maybe something changed on your side since then?

[robcresswell]

@GiovaniGuizzo If I install 1.12.0 in my env, then change it to 1.13.0, the env breaks. If I install 1.12.0 it works again. I'll dig more.

[robcresswell]

I figured it out; I was using 1.13.0 sidequest core, and 1.12.0 as the db backend, which was giving this error and resulting my dep tree having multiple versions core in it. Sorry for the noise