I have an app that has been working without issues for the past several months. As of yesterday evening, I deployed the app using the same deploy script I’ve been using for months, and all of a sudden the code changes I’m making aren’t showing up.
I am at a complete loss as to the root cause here. The line in my deploy script that does the actual deployment is fly deploy --app resybot-dev --config fly.dev.toml --image-label latest
The deployment completes successfully each time, and yet the code changes I make locally don’t appear in the app.
I’m happy to provide any other information. Any guidance or assistance would be greatly appreciated!
If it was working for you before then it’s probably related to the recent registry changes. I’m assuming you’re building and pushing the new image to the registry? Try tagging by a different name.
When I look at my Registry in fly.io’s dashboard, I see the exact same created and updated date for every version since v322 (I’m at v344) other than one (v331). All of the matching ones have a created/updated date of Oct 11, 2025 02:45 UTC. It’s currently Oct 12, 2025 02:56 UTC. v331 has a created/updated date of Oct 11, 2025 21:52 UTC.
Is that also connected to the registry update? Is using the same tag (e.g. latest) now an issue?
I don’t have much insight into the latest registry changes, only that it has caused some issues. IIRC, the latest tag isn’t properly working… so try tagging something else, eg branch-name
It’s difficult to know how to advise here. I’ve only ever used latest on a few of my apps, and I’ve not noticed this problem at all. I wonder if it is region-dependent?
The Fresh Produce section is where these are usually announced—although sometimes also the hidden category, Operations, the email newsletter, or the blog. (Unfortunately the much-appreciated Infrastructure Log seems to have been retired now, but that was a fifth source of early hints in the past.)
I think @khuezy is referring to the following in particular from Fresh Produce: