---
title: "Releases"
description: "How the plugin and hooks are released as signed bundles, how a project pins one, and how to list, update and roll back."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.overlane.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Releases

The Overlane plugin and hooks reach your machine as signed releases. A project pins one release, so every agent on it runs the same files. An update is verified against the signed manifest and never changes files under a running task.

```sh
overlane release list
overlane release status
```

[`release list`](/cli/release-list/) shows each release with its version, short digest, channel, change kinds, restart rule, compatibility and which projects pin it. [`release status`](/cli/release-status/) compares the installed release with the project's pin and works when the service is down.

## Update

```sh
overlane release update --dry-run
overlane release update
```

[`release update`](/cli/release-update/) verifies the signature, shows the file diff and runs the agents' native update commands. A release that changes executable files or policy needs `--approve` with its digest, so a change like that is always a deliberate step. Use `--to DIGEST` to install a specific release.

## Roll back

```sh
overlane release rollback --force
```

[`release rollback`](/cli/release-rollback/) moves the project's pin back one release and installs it the way `update` does. It reverts the project's release, so without a terminal it needs `--force`.

Source: https://docs.overlane.app/releases/index.mdx