v1.0.6
Fixes
- Restore authenticated commands. Liftoff retired the
v2-12-2API host with"The server is deprecated.", breaking every authenticated subcommand once the cached access token expired. Default bumped tov2-12-3. (#15) - Better error on future deprecations. When the backend returns the deprecation marker (from
auth refresh,auth login, or any tRPC query), the CLI now points users at theLIFTOFF_API_BASEworkaround instead of surfacing the bare upstream message. (#15)
New
LIFTOFF_API_BASEenv var override. Dodge the next API host retirement without waiting for a release:The Liftoff iOS/Android app shows its version under Settings → About; matching that is usually safe. The CLI logsLIFTOFF_API_BASE=https://v2-XX-Y.api.getgymbros.com liftoff-export workouts list
liftoff-export: using LIFTOFF_API_BASE=<value>to stderr once on first use. (#15)- Weekly automated host-rotation probe.
.github/workflows/api-host-probe.ymlruns Mondays at 14:00 UTC; if the default host gets retired, it scans candidate versions and opens a PR bumpingdefaultAPIBase. (#16)
Notes
Existing users do not need to re-authenticate — tokens in ~/.config/liftoff-export/auth.json remain valid against the new default host.