npx @buildinternet/releases get fly-ioManaged Postgres reaches fuller API coverage this month, while flyctl's internal request stack completes a shift from GraphQL toward the Machines API.
Managed Postgres storage and connectivity deepened. The fly-go client added user, extension, and attachment endpoints across v0.9.12–v0.9.13, followed by storage fields on the flaps client in v0.11.1. The mpg status command now shows used and provisioned storage, and connect and proxy now route through the public Machines API rather than an internal path, decoupling proxy readiness from credential state.
GraphQL replaced with Flaps and ui-ex. flyctl v0.4.101 moved org selection, release lookups, and compact app lookups from GraphQL to Flaps and the ui-ex API. App and region reads that only touch Flaps-available fields now go direct to Flaps, trimming the client and reducing cross-service dependencies.
Networking surface broadened. Egress IP types landed on the Machines API in fly-go v0.9.14, and 6PN network data was added to IP assignment responses in v0.9.15. A Flycast IP allocation bug on first deploy for default-network apps was fixed in flyctl v0.4.105.
Volume proportional autogrow added. fly-go v0.10.0 introduced support for proportional autogrow on volumes, and app creation now accepts an idempotency key, making retried creates safe.
Security and diagnostics tightened. Credentials are now redacted from debug-logged HTTP bodies (fly-go v0.11.0), kubeconfig files are written at owner-only permissions, and the MCP client configuration is written at 0600. Capacity errors are classified by scope, and cancellation causes are propagated through contexts and traces.