Turn new upstream releases into tickets, automatically.
A self-hosted release monitor with a web UI. It creates a ticket when a real new release ships.
Stop watching release pages.
Keeping dependencies, base images and upstream tools current usually means watching release pages or wading through notification noise. Release Ops watches the projects you care about and puts each new release where your team already plans work, as a ticket.
Sources and tickets
Any source can feed any ticket integration, per monitored repo
Release sources
GitHub · GitLab · Gitea · Forgejo · Codeberg
Release Ops tracks the latest stable release of each monitored repo.
Ticket integrations
Kaneo · Jira · Linear
One integration can serve several ticket projects, each with its own status mapping.
How it behaves
The first poll of a repo only records a baseline. Tickets are created on a real tag change.
Per ticket project: supersede (the default), merge into the open ticket, or skip if one is open.
Map each ticket project’s open, done, cancelled and superseded statuses, and customise the title, description and supersede comment.
Set the interval in the UI, or run a poll on demand.
Shoutrrr targets such as Slack, ntfy or Discord on create, error and supersede events.
SQLite on a volume. No Redis, Postgres or multi-service Compose.
Release Ops v0.1.0 is out. It is self-hosted open source under AGPL-3.0. The image is ghcr.io/mdg-labs/release-ops.