v0.2.74
v0.2.74 — Stop re-prompting for OpenRouter key on upgrade
Patch release that fixes a CLI annoyance: tale upgrade / tale deploy no longer interrupts existing installs with an OpenRouter API key prompt when the local secrets file is absent. Operators who configure OpenRouter through Settings → AI providers (or use a different provider entirely) are no longer blocked at the terminal.
🐛 Fixes
- Stop prompting for an OpenRouter API key during partial
.envupgrade. The interactive password prompt was only meant for first-install onboarding; on the.env-already-exists path the CLI now emits a non-fatal warning instead, so deploy/upgrade stays unattended for users who have already provisioned the key elsewhere (#1738)
Upgrade
No manual migration required. Run tale upgrade to update the CLI, then tale deploy to apply the new version.
Contributors
Full Changelog: v0.2.73...v0.2.74