reflex-dev/reflex reflex-hosting-cli-v0.1.70

reflex-hosting-cli@0.1.70

on GitHub

Deprecations

• reflex cloud deploy is renamed to reflex cloud gcp-standalone, deprecated as of 0.1.70 and removed in 0.2.0. Inside the reflex cloud group, deploy meant the standalone gcloud script runner while reflex deploy meant the managed platform deploy — one namespace apart, opposite semantics. The old name still works and is hidden from help; invoking it warns, naming both the new name and the managed path. (#6908)

Features

• deploy() accepts gcp_connection, full_deploy and strategy. gcp_connection resolves a named GCP connection and pins the app to it (provider_account_id on the provider write), instead of every CLI deploy landing on the organization's default connection. full_deploy is written before the hostname is reserved, so the reserve hands back the single provider origin the frontend is then compiled against. All three can also be set in the config file. (#6908)
• reflex cloud providers list (also reachable as providers connections) now lists each connection's name, default marker and runtime service account, so there is something to pass to reflex deploy --gcp-connection. providers status lists the same connections. A member who may not read the organization's stored provider accounts still gets the connection names, from the GCP status; their runtime identities are reported as unreadable rather than as the project default. (#6908)

Bug Fixes

• Optional settings in cloud.yml / pyproject.toml are validated again on Python 3.10–3.13. A X | None annotation reports as types.UnionType there, which the config validator did not recognize, so every optional field went unchecked on those versions while being checked on 3.14 — a quoted full_deploy: "false" was sent to the server as a truthy string, and a non-string hostname or gcp_connection failed later with a TypeError instead of a config error. (#6908)