---
title: "updates in config.yaml"
url: https://devlanes.run/docs/reference/config/user/updates/
description: "Reference for the updates key in ~/.devlanes/config.yaml."
---

# updates in config.yaml

A top-level key of [`~/.devlanes/config.yaml`](/docs/reference/config/user/).

## `updates`

Type: mapping.

Release checks: whether the daemon looks for newer devlanes releases (`mode`), and whether the TUI shows release highlights after an update (`highlights`).

```yaml devlanes-user
updates:
  mode: disable
```

### `updates.highlights`

Type: boolean. Default: `true`.

Show the release highlights dialog the first time the TUI opens after an update; defaults to true. Set false to skip the dialog. The new version still counts as seen, so turning this back on does not show the highlights of releases you already skipped.

```yaml devlanes-user
updates:
  highlights: true
```

### `updates.mode`

Type: string. Default: `auto`.

What devlanes does about newer releases: `auto` (the default) checks every 4 hours and when the TUI opens, shows the new version and installs patch releases in the background where the install method allows it; `notify` only shows the new version; `disable` never checks. `DEVLANES_NO_UPDATE_CHECK=1` or a CI environment also turns checks off.

Values:

- `disable`: Never look for releases; nothing is read from the network.
- `notify`: Read the latest version from the registry devlanes was installed from, and show it in the TUI and in command output when it is newer. Nothing is installed; run `devlanes update` to install it.
- `auto`: The default. Read the latest version from the registry devlanes was installed from, show it in the TUI and in command output when it is newer, and install patch releases in the background where the install method allows it; they apply the next time you start devlanes at a terminal. Minor releases, which can break things before 1.0, still wait for `devlanes update`.

```yaml devlanes-user
updates:
  mode: disable
```
