We’ve been doing a bit of spring cleaning in flyctl—the kind that doesn’t change how you deploy, but hopefully makes things a little clearer day to day.
1. Deprecated regions, begone.
The fly platform regions command (and a few friends) now automatically filter out regions that have been deprecated. No more wondering why that mysterious xyz region shows up even though you can’t actually deploy there. What you see now reflects what you can really use. As a bonus, if you don’t specify a region to launch in, we won’t suggest you deploy it somewhere that doesn’t exist anymore.
2. Saying goodbye to old “launch plan” ghosts.
We’ve also scrubbed out some confusing terminology left over from older versions of flyctl. Mentions of “launch plans” and a few other retired features have been removed to better reflect how Fly.io works today.
This isn’t a flashy release—just some thoughtful cleanup to make flyctl more consistent and predictable.
If you spot anything else that feels out of date, we’d love a heads-up. You can open an issue on GitHub or leave a note right here.