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.

Minimum safe checklist:

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

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

• Export provider-side data before risky changes: Standalone Scripts.

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

GitHub releases (source of truth)

GitHub has the authoritative list:

• https://github.com/cenodude/CrossWatch/releases

Related topics

• Docker setup

• Maintenance

• Configuration (config.json)

• Disclaimer

Summary

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

Next steps

• Read the latest major version notes: Version 0.7

• Confirm the exact build you’re on in GitHub releases: https://github.com/cenodude/CrossWatch/releases