Neon CLI command: deploy
Apply a neon.ts policy to a branch
The deploy command applies a neon.ts policy to a branch. It is a top-level alias of neon config apply, with the same options.
neon deploy [options]| Option | Description | Type | Default | Required |
|---|---|---|---|---|
--allow-protected |
Auto-confirm applying to a branch marked protected on Neon | boolean | false |
No |
--branch |
Branch ID or name | string | — | No |
--config |
Path to a neon.ts policy (defaults to walking up from cwd) | string | — | No |
--env |
Path to a .env file to load into the environment before evaluating neon.ts so Function env values resolve from it. Existing env vars are not overridden. Function env values that read process.env must be set in this file or the environment. | string | — | No |
--env-pull |
Pull the branch's Neon env vars (DATABASE_URL, …) into a local .env after a successful apply. On by default; use --no-env-pull to skip (e.g. when injecting env at runtime with neon-env run / neon dev). |
boolean | true |
No |
--project-id |
Project ID | string | — | No |
--update-existing |
Auto-confirm overriding existing remote settings on the branch | boolean | false |
No |
For non-interactive use (scripts, CI, agents), pass --update-existing and --allow-protected to auto-confirm the corresponding prompts.
neon deploy --branch feature/auth --update-existing