When I run fly deploy with the "--image-label" flag, why does it deploy an older version of my code?

Hi @gkpo,

Yes, we did make some registry-related changes this past week, see Faster, more reliable image deploys for all remote builders for some general details. It’s possible that mutable tags (like latest) that are overwritten aren’t matching their original expected behavior.

Thanks for reporting this issue, we’ll look into this and if it is a registry issue, hopefully restore the original mutable-tag behavior soon. In the meantime, you can try a deploy with the --depot=false flag (legacy builders don’t currently use the same registry optimizations) to see if that still works as expected for you.