Release 4.1.2

Improvements

• #67
• #66

Release 4.1.1

Features

• #59

Bug Fixes

• #63
• #62

Release 4.0.0

Improvements

• Switch to config-based inlets format (#58)

Release 3.3.1

Bug Fixes

• #46

Release 3.3.0

Improvements

• Added Grafana Alerts inlet (#45)

Release 3.2.0

Improvements

• Whitelist (#44) (thanks to @JokerQyou)

Release 3.1.1

Improvements

• #39
• #36

Release 3.0.0

With the release of version 3, Webhook2Telegram was rebranded to Telepush, with an official, freely available instance hosted at telepush.dev. Besides a new name and a new logo, a couple of thing have changed, including breaking changes. As a consequence, Telepush v3 is not backwards-compatible with earlier versions. You might want to update your script.

Breaking Changes

• Docker image was renamed from n1try/webhook2telegram to ghcr.io/muety/webhook2telegram
• Recipient token is now encoded as a path parameter, instead of included inside the payload. Routes have changed, e.g. from /api/messages to /api/messages/<recipient>, while the recipient_token field was removed from a message's JSON schema
• Inlets were renamed (and their routes, accordingly)
  • alertmanager_webhook ➡️ alertmanager
  • bitbucket_webhook ➡️ bitbucket
  • webmentionio_webhook ➡️ webmentionio

Hosted Service

The demo instance at https://apps.muetsch.io/webhook2telegram will be shut down. Please migrate to telepush.dev.

Release 2.4.1

Improvements

• #30
• #29

⚠️ Important: Docker image has changed from n1try/webhook2telegram to ghcr.io/muety/webhook2telegram 🐳.

Release 2.3.2

Features

• #26

Improvements

• #19