Release-bot

A Telegram bot that monitors the releases of given repos, sending messages upon a new release.

  • Automation
  • Cloud
  • Communication
  • Other
  • Productivity
  • Tools & Utilities
A Telegram bot that monitors the releases of given repos, sending messages upon a new release.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

56/100 Fair

Maintained
60last commit 157 days ago
Popular
3769 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
95no serious findings, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed 13 days ago, links checked 18 days ago

GitHub stars
69
Open issues
8
Last commit
2026-06-17
Latest release
v0.8.3
License
MIT
Activity
stale

Checked 6 days ago - source: GitHub (JanisV/release-bot)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install release-plz first Use `pacman -S release-plz` on Arch, `apk add release-plz` on Alpine, or install Rust (a programming language) first and then run `cargo install --locked release-plz` on other systems. Without the installed `release-plz` command, later steps will fail because the app is missing. source
  • Arch: use the stable package On Arch, prefer `pacman -S release-plz` over the AUR (Arch User Repository) `release-plz-git` package unless you specifically want a moving Git build. Mixing these up can install a less stable version and make later behavior confusing. source
  • Shell completion is optional You can save the completion command for your shell to get auto-suggestions while typing `release-plz`. This is only a convenience, so skipping it will not break the installation. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do I need a public IP or domain to run release-bot?

No, it can work locally without a white IP and domain name. Only a Telegram bot token is required.

Is a GitHub token required for release-bot?

No, GITHUB_TOKEN is optional. Without it the bot works well for about 20 repos, while a classic or fine-grained GitHub token can be set if needed.

How do I keep release-bot data when using Docker?

Mount a host directory to /app/data as a volume in Docker Compose or docker run.

Which port does the Docker example use for release-bot?

The Docker examples map host port 5000 to container port 5000.

What ways can I subscribe release-bot to repositories?

You can subscribe by owner/name, GitHub, PyPI, or npm URL, upload a requirements.txt or package.json file, or subscribe to starred repos.

Answers sourced from github.com

Community

Collected 49 days ago - public community threads