> For the complete documentation index, see [llms.txt](https://wiki.crosswatch.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.crosswatch.app/related-information/release-notes.md).

# Release notes

What changed between versions, plus quick upgrade guidance.

Use release notes to plan upgrades. Catch breaking changes early.

Major versions have their own page (example: `Version 0.7`).

Patch releases nest under the major version (example: `v0.7.8` under `Version 0.7`).

### Quick rules

* If you skip versions, read **every major version** you cross.
* Start with **Migration / first-run notes** and **breaking changes**.
* Treat patch releases as fixes unless called out.

### Before you upgrade

{% hint style="warning" %}
Back up first. Always test your restore at least once.
{% endhint %}

{% stepper %}
{% step %}

### Back up `/config`

Create a backup before you change versions.
{% endstep %}

{% step %}

### Read every major version you cross

Do not skip migration notes or first-run warnings.
{% endstep %}

{% step %}

### Upgrade and hard refresh

After major UI changes, refresh the browser fully.
{% endstep %}
{% endstepper %}

Minimum safe checklist:

* Back up your `/config` directory (Docker) or `CONFIG_BASE`.
* Snapshot local tracker state (if you rely on it): [Adapter: CrossWatch](https://wiki.crosswatch.app/crosswatch/settings/synchronization/others/cw.md).
* Export or capture critical data before risky changes: [Captures](https://wiki.crosswatch.app/crosswatch/main-dashboard/navigation/captures.md).
* Upgrade CrossWatch.
* Hard refresh your browser after major UI changes.

### Where to start

* New install or big jump: start at the latest major version page.
* Upgrading one patch: read the patch entry and any notes under the major.

Latest major:

* [Version 0.14](https://wiki.crosswatch.app/related-information/release-notes/version-0.14.md)

### Common upgrade helpers

<table data-view="cards"><thead><tr><th>Title</th><th data-card-target data-type="content-ref">Open</th></tr></thead><tbody><tr><td>Create and restore backups</td><td><a href="https://wiki.crosswatch.app/crosswatch/main-dashboard/tools/backup-and-restore.md">Backup &amp; Restore</a></td></tr><tr><td>Review config file behavior</td><td><a href="https://wiki.crosswatch.app/crosswatch/advanced-and-api/configuration-reference.md">Configuration reference</a></td></tr><tr><td>Check current limitations</td><td><a href="https://wiki.crosswatch.app/getting-started/limitations.md">Limitations</a></td></tr><tr><td>Read the latest major notes</td><td><a href="https://wiki.crosswatch.app/related-information/release-notes/version-0.14.md">Version 0.14</a></td></tr></tbody></table>

### GitHub releases (source of truth)

GitHub has the authoritative list:

* <https://github.com/cenodude/CrossWatch/releases>

### Related topics

* [Docker setup](https://wiki.crosswatch.app/getting-started/installation.md)
* [Maintenance](https://wiki.crosswatch.app/crosswatch/settings/maintenance.md)
* [Configuration (config.json)](https://wiki.crosswatch.app/crosswatch/advanced-and-api/configuration-reference.md)
* [Disclaimer](https://wiki.crosswatch.app/related-information/disclaimer.md)

### Summary

Read each major version you skipped. Back up before you change anything.

### Next steps

* Read the latest major version notes: [Version 0.14](https://wiki.crosswatch.app/related-information/release-notes/version-0.14.md)
* Confirm the exact build you’re on in GitHub releases: <https://github.com/cenodude/CrossWatch/releases>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.crosswatch.app/related-information/release-notes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
