Changelog
Where to find OpenTickly release notes, how releases work, and how to upgrade.
Release notes live on GitHub Releases. This page covers how releases work and how to upgrade.
- Latest and historical releases: github.com/CorrectRoadH/OpenTickly/releases
- Full commit history: github.com/CorrectRoadH/OpenTickly/commits/main
- Docker images: hub.docker.com/r/correctroad/opentickly
How releases are cut
Each release is a git tag on main. Tagging it automatically publishes a new Docker image and updates the demo at track.opentoggl.com. To upgrade a self-hosted instance, run docker compose pull && docker compose up -d.
Upgrade notes
Usually you just upgrade, nothing else to do. The database is updated automatically when the server starts, and the Toggl-compatible API doesn't change, so your integrations keep working.
If a release does need extra steps, its GitHub Release has an Upgrade section explaining them. No such section means a normal upgrade.
If an upgrade fails, open an issue with the version, the step that failed, and the full log.
Staying compatible with Toggl
OpenTickly follows Toggl's public APIs: Track v9, Reports v3, and Webhooks v1. CLIs, MCP tools, and integrations that work with Toggl should keep working after each upgrade. When Toggl adds or changes an endpoint, we aim to catch up in the next release.