---
title: "wendy app release"
description: "Record a release of this project's app in Wendy Cloud"
---

## Syntax

```sh
wendy app release [flags]
```

## Examples

```sh
wendy app release --help
```

## Arguments

No positional arguments are declared in the command synopsis.

## Flags

Flags below include inherited options. Types and defaults come from the CLI source. An empty default means no value is configured.

| Flag | Type | Default | Description |
| --- | --- | --- | --- |
| `--cloud-grpc` | string | (empty) | Cloud gRPC endpoint of the session to use |
| `--device` | string | (empty) | Target device `host` (hostname, IP, or host:port); 'wendy run' accepts a comma-separated list to deploy one build to several devices (needs a remote build host and --detach). Defaults to $WENDY_DEVICE, then the saved default device |
| `--digest` | string | (empty) | Image manifest digest, sha256:<hex> (required) |
| `--json` | bool | `false` | Output in JSON format |
| `--tag` | string | (empty) | Release tag, e.g. v1.4.0 (required) |

## Output

Output depends on the operation and selected target. [Command behavior and detailed examples](../../../../advanced/clients/wendy-cli/commands/app/release/).

## JSON output

The global `--json` option requests machine-readable output. The CLI also selects JSON mode when no interactive terminal is attached. Support and payloads are command-specific; this flag does not guarantee a single JSON document for commands that stream logs or invoke build tools. Consult Details before parsing command output.

## Exit codes

The CLI entry point returns `0` on success and for its user-cancelled or default-cleared results. Other returned errors exit with `1` and print a diagnostic to stderr. Some operations may terminate through subprocess or signal handling; do not infer application health from the CLI exit code alone.

## Common errors

Check argument values and flag combinations against the synopsis above. For discovery, build, port, and readiness failures, see [deployment troubleshooting](../../../../errors/). Command-specific constraints are in Details.

## See also

- [wendy app](../../../../reference/cli/app/)
- [CLI conventions and configuration](../../../../reference/)

## Details

Records a release of the app in wendy.json: a tag naming one image digest.
Both --tag and --digest are required; a release is never implicitly 'latest'.
To record a deploy as it happens, use 'wendy run --record-release <tag>' instead.

[Command behavior and detailed examples](../../../../advanced/clients/wendy-cli/commands/app/release/)