Repository navigation
Releases
v1.1.1
Changed
notifier_messages_sent_totalhas a newresult="retried"for a failed attempt that a later one replaced (a
rich message sent again as classic, a keyboard sent again as links).result="error"now counts only messages
that were not delivered, so the "Failed sends, 24h" stat no longer includes recovered sends.- The web panel says when rich messages are off (
RICH_MESSAGES=falseor nosendRichMessageon the Bot API
server) and marks the chats that get classic messages instead of the look they chose.
Fixed
- Very large events (hundreds of labels, huge bodies) could exceed Telegram's limits: the classic message is now
kept within 4096 characters and the rich message within 32 768 characters of HTML, dropping listed items, the
quote, notes and then long field values, in that order. The heading, item, repository and buttons always stay. - A rejected rich message is logged once per kind of error instead of once per byte offset, and the set of logged
errors is bounded. /configure:- a failed topic creation keeps the buttons, so the choice can be made again without running the command;
- the button stops spinning while the topics are being created;
- in a regular group nothing is saved until a button is pressed;
- when the bot cannot check who is an administrator and the command came from an anonymous administrator,
the alert explains what to do instead of saying "only administrators".
/statusin a regular group says that topic routing is off.
What's Changed
- fix: keep messages within Telegram limits and close the 1.1.0 review leftovers by @marensovich in #27
- Release 1.1.1: message size limits, accurate failure metrics, /configure fixes by @marensovich in #28
Full Changelog: v1.1.0...v1.1.1
v1.1.0
Added
-
Local read-only web panel (
PANEL_ADDRESS, e.g.127.0.0.1:8081): overview with warnings for repositories
without a webhook secret, the list of connected repositories and their chats, and every chat with its topics
and event routing. It listens only on loopback unlessPANEL_ALLOW_REMOTE=true, rejects non-loopbackHost
headers, accepts onlyGET/HEAD, never shows secrets, and needs no internet access. Open it through an SSH
tunnel:ssh -L 8081:127.0.0.1:8081 user@server. -
Delivery log and deduplication: every incoming webhook is recorded (metadata only) with its result —
delivered,ignored,rejected,failedorduplicate. A redelivery of an already delivered webhook
(X-GitHub-Delivery, GitLabIdempotency-Key/X-Gitlab-Event-UUID) is answered with200 DUPLICATEand
not posted again. The log is pruned hourly afterDELIVERIES_RETENTION_DAYS(default 14,0keeps it). -
Health report: JSON with version, uptime and
db/telegramchecks;503when one fails, with the error.
The Telegram check uses agetMeprobe once a minute and successful sends, never a call per request. -
Prometheus metrics at
/metrics(METRICS_ENABLED, default on): webhooks by platform/event/status, webhook
handling time, send attempts by result, build info and start time.METRICS_ADDRserves them on a separate
address such as127.0.0.1:9090. No new dependencies. Grafana dashboard indocs/grafana-dashboard.json. -
Docker image on GitHub Container Registry for
linux/amd64,linux/arm64andlinux/arm/v7:
ghcr.io/marensovich/github-gitlab-notifierwith tagsX.Y.Z,X.Y,latest(stable releases only) and
edge(every push todevelopment).docker-compose.ymlnow pulls this image;--buildstill builds locally.
The Dockerfile cross-compiles in the build stage instead of emulating the target platform. -
Golden tests for notifications: every handler is rendered from payload fixtures in
internal/handler/testdata/<platform>/<event>/in every language and compared with.goldenfiles
(go test ./internal/handler -run TestGolden -updateregenerates them). All 19 events are covered, including
force pushes, branch creation/deletion, 50-commit pushes, pull requests from forks, drafts, pre-releases,
confidential GitLab issues and notes, notes on issues and skipped actions.scripts/scrub-fixture.shcleans a
real payload before it becomes a fixture. -
GitLab confidential issues, comments on them and internal notes are marked with 🔒 "Confidential — visible only
to project members in GitLab", so the chat sees that the text was not public in the project. -
New notification look using Telegram rich messages: a heading, the item as a bold link, a compact table of
repository, branch and other details, long text in an expandable quote, commit and file lists collapsed under a
summary, coloured buttons ("Open PR", "Compare", "Open run"…) and a footer with the author and the event time,
shown relative in the reader's language and time zone. If Telegram rejects a rich message, the classic message
is sent instead (counted innotifier_rich_fallbacks_total).RICH_MESSAGES=falseturns rich messages off for
the whole installation. -
/configureis a short setup with buttons, edited in place: in a forum chat it asks whether to create topics or
post everything to the main chat, then every chat picks the new look or the classic one (for old and third-party
Telegram clients, which show rich messages as unsupported). Current choices are marked with ✓; run it again to
change them. Only chat administrators can press the buttons. The web panel and/statusshow each chat's look
and topic routing;/statusalso says when the new look is off on the server.
Changed
- Classic notifications use the same layout as the new look and carry their links as coloured inline buttons.
/configureworks in regular groups too (it skips the topics step and posts to the main chat) instead of
refusing them.notifier_messages_sent_totalhas aformatlabel (rich/classic); dashboards that sum it by
messenger, resultkeep working. The Grafana dashboard splits "Messages sent" by format and shows rich fallbacks.- Database migration
0003addsformat(defaultrich) anduse_topics(default on) to every chat, so an
upgraded installation gets the new look with the same routing. GET /healthand/webhook/healthreturn the health report (same as the new/healthz) instead ofpong,
and answer503when the database or Telegram is not working. Monitors that compared the body withpong
need to check the status code instead. The installer prints the report when the check fails.- The database schema is now versioned (
schema_versiontable, numbered SQL files instorage/migrations/).
Pending migrations run at start-up, each in its own transaction; a failed one is rolled back and the bot stops
with the name of the migration. Databases from 1.0.x are recognised and marked as version 1 without changes.
A database written by a newer version is refused instead of being opened by an older binary.
Fixed
- Push notifications for created and deleted branches read "Branch deleted to branch …" / "Удалена ветка в ветку …";
they now say "Deleted branch …" / "Удалена ветка …". - Pull requests from forks showed the source branch without its owner (often
main→main); they now show
owner:branch. - A slow
setMyCommandsat start-up (Telegram answering504after minutes) kept the webhook port closed until it
gave up; the command menu is now registered in the background.
What's Changed
- feat(web): add a local read-only admin panel by @marensovich in #16
- feat: versioned schema migrations and webhook delivery log by @marensovich in #17
- feat: add /healthz and Prometheus metrics by @marensovich in #18
- fix: make /health return the full health report by @marensovich in #19
- feat: publish a multi-arch Docker image to GHCR by @marensovich in #20
- test: golden tests for every notification handler (NTF-05) by @marensovich in #21
- feat: mark confidential GitLab issues and notes by @marensovich in #22
- feat: rich-message notifications with per-chat look and topics in /configure by @marensovich in #23
- fix: start webhooks without waiting for the command menu and polish /status by @marensovich in #25
- Release 1.1.0: rich messages, /configure, web panel, metrics by @marensovich in #26
Full Changelog: v1.0.1...v1.1.0
v1.0.1
Security
- Update
github.com/klauspost/compressto 1.18.7 (indirect dependency of the Telegram client) to fix
GHSA-259r-337f-4rfw / CVE-2026-63209
(integer overflow and out-of-bounds write, severity high).
What's Changed
- fix(deps): update klauspost/compress to 1.18.7 (GHSA-259r-337f-4rfw) by @marensovich in #12
- Release 1.0.1: security update for klauspost/compress by @marensovich in #13
Full Changelog: v1.0.0...v1.0.1
v1.0.0
First stable release: complete GitHub and GitLab support, one-command Linux installation and Docker image.
Pre-built binaries: Linux (amd64, arm64, armv7), macOS (Intel, Apple Silicon), Windows (amd64, arm64),
FreeBSD (amd64, arm64).
Added
- GitHub events:
pull_request,pull_request_review,issues,issue_comment,release,workflow_run,
fork,ping; tag pushes are shown as "New tag" / "Tag deleted". - GitLab events: Push, Tag Push, Merge Request, Issue, Confidential Issue, Note, Confidential Note, Pipeline and
Release hooks. User links work with self-hosted GitLab. - Forum topics for Pull Requests, Issues, Releases and CI/CD in addition to Stars and Pushes.
- Commands
/status,/lang,/version,/disconnect; command list in Telegram's Menu button. - Per-chat notification language.
- Webhook signature verification (GitHub
X-Hub-Signature-256, GitLabX-Gitlab-Token) with per-repository secrets
shown by/connectand an optional globalWEBHOOK_SECRET. - Notifications of a connected repository are delivered only to the chat it was connected from.
- Linux installer
scripts/install.shwith a hardened systemd service (install, update with rollback, uninstall). Dockerfile(distroless, non-root) anddocker-compose.yml.- CI workflow (gofmt, vet, race tests, shellcheck, Docker build) and a Build workflow that cross-compiles all
platforms on every push tomaster. - Release binaries for linux/armv7, windows/arm64 and freebsd/arm64; the installer supports 32-bit ARM.
- Configuration:
BOT_LANG,DB_PATH,WEBHOOK_SECRET,NOTIFY_UNKNOWN_EVENTS,TELEGRAM_API_URL;
flags--configand--db;/healthendpoint. - Graceful shutdown on SIGINT/SIGTERM.
- Tests for handlers (real payload fixtures), server, storage, bot command parsing and translations.
CONTRIBUTING.md,SECURITY.md,.editorconfig,.gitattributes.
Changed
- Translations are embedded into the binary; the bot no longer depends on the working directory.
- Unsupported events (e.g.
check_suite,watch) are ignored instead of posting "New event …" messages. CHAT_IDis optional (fallback only)./configurecan be re-run to add new topics; it keeps the chat language./connectaccepts any GitHub/GitLab URL including self-hosted GitLab, keeps the secret on reconnect and works before
/configure.- Release workflow uses the Go version from
go.mod, builds macOS arm64, produces static binaries and checksums.
Fixed
- Commit messages, titles and file names containing
<,>or&broke Telegram messages (HTML is now escaped). - Cyrillic commit messages were cut in the middle of a character.
SERVER_ADDRESSwas ignored.- Crash on commands sent by anonymous group admins.
- "FOREIGN KEY constraint failed" when
/connectwas used before/configure. go vetwarnings; unused BoltDB dependency removed.
What's Changed
- feat(core): add GitHub issue and PR templates by @marensovich in #1
- development by @marensovich in #2
- Complete event handlers, systemd installer, Docker and CI by @marensovich in #3
New Contributors
- @marensovich made their first contribution in #1
Full Changelog: v.0.0.1...v1.0.0
v.0.0.1
🚀 First Public Release v0.0.1
GitHub-GitLab Notifier — self-hosted Telegram bot for Git repository notifications.
Highlights
- ✅ GitHub webhooks: push, star, pull_request, issues
- ✅ Forum topics auto-creation via
/configure - ✅ SQLite database with
/statusviewer - ✅
/connectcommand for webhook URL generation - ✅ i18n: Russian + English (auto-load from GitHub)
- ✅ Proxy support (HTTP/SOCKS5)
- ✅ Cross-platform builds (Linux, macOS, Windows, FreeBSD)
Full Changelog: https://github.com/marensovich/GitHub-GitLab-Notifier/commits/v.0.0.1