Skip to content

Install the neon CLI during init, not the retired neonctl alias - #432

Merged
andrelandgraf merged 1 commit into
mainfrom
fix/init-install-neon-not-neonctl
Aug 14, 2026
Merged

Install the neon CLI during init, not the retired neonctl alias#432
andrelandgraf merged 1 commit into
mainfrom
fix/init-install-neon-not-neonctl

Conversation

@philip

@philip philip commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Overview

neon init was still probing for, version-checking, and installing the old neonctl package. This switches it to the current neon CLI:

  • Version detection probes neon first and keeps neonctl as a fallback, so an existing global neonctl install still counts as installed and isn't reinstalled.
  • The "is it up to date" check reads npm view neon.
  • The global-install symlink check looks under both the neon and neonctl module paths.
  • Auth (neon me) and DATABASE_URL context resolution shell out to neon.

The command strings emitted to users and agents already said neon; this aligns the detect/install machinery behind them. Split out of #431 so it can be reviewed and merged on its own.

This pull request and its description were written by Isaac.

`neon init` was still probing, version-checking, and installing the old
`neonctl` package. Switch it to `neon`: version detection tries `neon`
first (and keeps `neonctl` as a fallback so an existing global install
still counts as installed), the update check reads `npm view neon`, and
the auth and context-resolution calls shell out to `neon`.

Co-authored-by: Isaac
@andrelandgraf
andrelandgraf merged commit ad7cf9a into main Aug 14, 2026
16 checks passed
@andrelandgraf
andrelandgraf deleted the fix/init-install-neon-not-neonctl branch August 14, 2026 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants