If possible, try updating flyctl to the latest version, or deploy with --depot=falseas a workaround if that doesn’t work. We’re still working on fixing up various edge-cases related to the recent registry changes, and older (pre-v0.3.180) flyctl versions have been tricky to get working.
Ah, version might actually be the issue. flyctl is installed with nix-darwin, so can’t update itself I don’t think. Will rip it out of there and install manually. Thanks for the heads up
As an aside, one of the deployments was via git/UI deployments so I presume it would have used the latest flyctl. That said, I’ll just do a depot=false locally if it happens again (which it did just now, only I go a registry 404.)