# Overview

Use release notes to plan upgrades, identify client-specific versions, understand behavioral changes, and validate the installation afterward.

## Where this lives

Open **Settings → About** to compare the installed version with the release notes.

Release notes explain what changed, which client or runtime version is affected, required migrations, security fixes, known limitations, and deprecated behavior.

> **Safety:** Install only signed official releases. Do not infer that the Desktop and CLI share a version number, and do not clear local data merely to resolve an update problem.

## Steps

1. Open **Settings → About** to compare the installed version with the release notes.
2. Use release notes to plan upgrades.
3. Identify client-specific versions.
4. Understand behavioral changes.
5. Validate the installation afterward.
6. Check the installed Desktop and CLI versions separately, read every release between the current and target versions, save active work, and preserve local-data exports before major upgrades.
7. **Confirm the result.** Restart the updated client and runtime, confirm the displayed versions, run diagnostics, and complete one small task, tool, and connection test relevant to your workflow.

## Choose the right path

- Read Latest release for the newest published change.
- Read V5 release notes when moving to the current product generation.
- Read Known limitations and Deprecated features before relying on older behavior.


## Confirm it worked

- Restart the updated client and runtime, confirm the displayed versions, run diagnostics, and complete one small task, tool, and connection test relevant to your workflow.
- The screen, command, file, run, or destination named in this guide reflects the expected state.