# atmos plugin delete

Delete a remote release by its immutable digest.

> ⚠️ Experimental

## Usage

```shell
atmos plugin delete <repository@sha256:digest> [--yes]
```

Deletion is irreversible. The command deletes one release by its immutable digest, so every tag that
points at that digest stops resolving. It does not touch other digests in the repository and it does
not edit discovery catalogs; unlist the release with
[`atmos plugin catalog remove`](catalog-remove.mdx) first, so no catalog advertises bytes that no
longer exist.

In an interactive terminal, Atmos looks up the release and asks for confirmation, showing the
repository, the digest, and the tags that will stop resolving. Declining leaves the release
unchanged. When standard input is not interactive (CI, a pipe, or a script), the command refuses
to run unless you pass `--yes`.

The registry must permit manifest deletion, and `on: plugin` policy can restrict it with the
`registry.delete` operation.

## Arguments and flags

- **repository@sha256:digest**
  Exact remote release digest, with or without the 
  oci://
   prefix. A tag is not accepted. Use the
  digest printed by 
  atmos plugin publish
  .
- **--yes, -y**
  Delete without asking for confirmation. Required when the command runs non-interactively.

## Examples

```shell
atmos plugin delete oci://registry.example.com/team/oidc@sha256:0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef
atmos plugin delete registry.example.com/team/oidc@sha256:<digest> --yes
```