aether deployment

aether deployment add MyApp Beta
aether deployment ls MyApp -k
aether deployment history MyApp Staging
aether deployment metrics MyApp Staging --from 2026-08-01 --to 2026-08-15
aether deployment rename MyApp Beta Canary
aether deployment clear MyApp Staging
aether deployment rm MyApp Beta

Subcommand	Flags	Purpose
add <appName> <deploymentName>	--key, -k	Create a deployment. -k supplies your own deployment key instead of a generated one, which matters when migrating from CodePush.
list, ls <appName>	--format, --displayKeys / -k	List deployments. -k includes the deployment keys.
history, h <appName> <deploymentName>	--format	List every release in the channel.
metrics, m <appName> <deploymentName>	--format, --from, --to	Show the daily install metrics behind the dashboard history charts.
rename <appName> <current> <new>		Rename a deployment.
clear <appName> <deploymentName>		Wipe the release history. Asks for confirmation; needs --force in non-interactive mode.
remove, rm <appName> <deploymentName>		Delete the deployment. Asks for confirmation.

Create, rename, clear, and remove are owner-only. Deployment concepts, including what the key does and does not protect, live on deployments and deployment keys.

Daily metrics

aether deployment metrics reads the same daily rollups the dashboard history charts draw from. deployment ls and deployment history show each release’s totals as they stand right now; this command shows one row per day and release label, so you can see how those totals got there.

aether deployment metrics MyApp Production
aether deployment metrics MyApp Production --from 2026-08-01 --to 2026-08-15
aether deployment metrics MyApp Production --format json

--from and --to are UTC dates in YYYY-MM-DD. Without them you get the last 30 days. The server narrows whatever you ask for to the retention window of the plan that owns the app, which is the owner’s plan rather than yours if you are a collaborator, and to the first day it recorded anything for that deployment. The range that comes back is often smaller than the one you sent, so the command prints the range it got. The server rejects a malformed date, or --from later than --to, with a 400.

Downloaded, installed, and failed are cumulative counters, and each cell shows the change since the previous calendar day in parentheses: 530 (+30). The comparison is per label, not per day, so a cell shows the counter alone whenever that label has no row for the day before: on the label’s first day, and after any gap in its series. Since every release mints a new label, the newest row on a release day is normally bare even when the rows above it are not. Active is a snapshot rather than a counter, so it never carries a change. Days with no data are left out instead of filled with zeros.

--format json prints the API response as it arrives, so a jq filter written against the endpoint works here unchanged. The CLI adds no envelope and renames nothing, which also means it gives you no shape of its own to rely on: when that response changes, this output changes with it.