Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

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

Back up first. Always test your restore at least once.

1

Back up /config

Create a backup before you change versions.

2

Read every major version you cross

Do not skip migration notes or first-run warnings.

3

Upgrade and hard refresh

After major UI changes, refresh the browser fully.

Minimum safe checklist:

  • Back up your /config directory (Docker) or CONFIG_BASE.

  • Snapshot local tracker state (if you rely on it): Adapter: CrossWatch.

  • Export or capture critical data before risky changes: Captures.

  • 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:

Common upgrade helpers

Title

Create and restore backups

Open
Backup & Restore
Title

Review config file behavior

Open
Configuration reference
Title

Check current limitations

Open
Limitations
Title

Read the latest major notes

Open
Version 0.10

GitHub releases (source of truth)

GitHub has the authoritative list:

Related topics

Summary

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

Next steps

PreviousTrakt vs SIMKL (Free plans)NextVersion 0.10

Last updated

Was this helpful?