Skip to content

v0.24.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 04 Nov 16:43
· 14 commits to main since this release
v0.24.0
258ba48
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's in this release

Everything here comes from #67. It smooths the last rough edges an AI agent hit while setting up DeployHQ for someone, with and without an existing account.

  • No account? The CLI says so. When nobody is signed in, the hints, dhq doctor and the --json recovery actions now also say that a person with no DeployHQ account runs dhq signup themselves, in a separate terminal. A wrong API key or "access denied" still points at dhq auth login only.
  • dhq signup switches the CLI to the new account, as dhq auth login does. If DEPLOYHQ_ACCOUNT or a .deployhq.toml (in the folder or a parent folder) still names another account, it warns, says which one wins and how to change it.
  • A mistyped branch is an error, not a silent switch. DeployHQ replaces a branch that isn't in the repository with another one. repos create / repos update --branch now fail when that happens, list the branches (up to 20) and give the repos update --branch command. A repository with no commits yet says to push one first.
  • Clearer errors: repos update on a project with no repository points at repos create instead of showing a 500. servers create for Static Hosting or a Managed VPS before beta enrolment points at dhq beta enroll --protocol <type>.
  • Small fixes: auth login asks again for an empty account name. After signing up, the next steps are for once the email is verified. Without a terminal, signup says the person has to run it themselves, instead of asking for --password.
  • For agents: dhq --help points at dhq skills install. The skill now says only a Managed VPS needs a payment method; Static Hosting doesn't.
  • Help text: templates commands --timing lists the accepted values (all, first, after_first), and deployment-checks --fail-on-unfixed-only describes what it really does (it fails only on findings that have a fix).

Worth knowing when upgrading

  • repos create / repos update --branch <name> now exit 1 when DeployHQ saved a different branch. Before, they reported success. The repository is still connected; fix the branch with dhq repos update --branch.
  • dhq signup now sets account in ~/.deployhq/config.toml to the new account.

Full detail is in CHANGELOG.md → 0.24.0.

Full Changelog: v0.23.0...v0.24.0

Assets 13
Loading