Release notes
What changed in every version of Thook, newest first.
2.8.0
Added
- Bitbucket Cloud: push (also branches and tags created and deleted), forks, builds, pull requests with approvals and comments, and issues. A build is one message that updates from running to the result. The bot gives a new endpoint,
/hooks/bitbucket/..., and the how-to has a page for it
2.7.0
Added
- Gitea and Forgejo (also Codeberg): push, branch and tag creation and deletion, forks, issues and comments, pull requests and reviews, releases, wiki changes, repositories and workflow runs. The bot gives a new endpoint,
/hooks/gitea/..., and the how-to has a page for it
2.6.1
Fixed
- Netlify: the link of a succeeded deploy preview or branch deploy opens that deploy and not the production site
2.6.0
Fixed
- Bug fixes and improvements
2.5.0
Added
- A release notes page on the site, with every version from 1.0.0
- Netlify: restored deploys (when a previous deploy is published again)
2.4.1
Fixed
- In channels,
/start,/rotateand/cleanupsometimes answered late or not at all
2.4.0
Added
/cleanupcommand:/cleanup ondeletes the progress message of a workflow, pipeline, job or deploy when the result arrives,/cleanup offkeeps it (default) and/cleanupshows the setting
Changed
- The progress of a workflow, check, deployment, pipeline, job or deploy (GitHub, GitLab, Netlify) is one message that updates from started to running. The result is a new message, so you are still notified. Updating a message is not counted in your usage
2.3.1
Changed
- The how-to explains the icons of the notifications
2.3.0
Changed
- The notifications are back to one icon per line (project, branch, commits, title, workflow, author): related data share a line, the author and the link are separated by an empty line and the link is the last line
2.2.1
Changed
- The preview image shown when the site is shared was refreshed
2.2.0
Added
- GitHub: workflow runs, issues, issue comments, pull request reviews, releases, deployment statuses and sponsorships
- GitLab: comments, releases and deployments
- Netlify: deleted deploys and deploy requests (pending, accepted, rejected)
Fixed
- A push to an open pull request is shown as "Pull request updated" instead of "Pull request synchronize"
2.1.0
Changed
- The notifications of GitHub, GitLab and Netlify show the details and the author in a quote under the title, the text of a person (error, description, form message) in italics, and the link of the event as a button
2.0.1
Changed
- The notifications have an empty line after the title and before the author
2.0.0
Changed
- The notifications of GitHub, GitLab and Netlify have a new, shorter structure (event and service, context, content with a link, who did it) with the full name of the project and clickable links to pull requests, issues, merge requests, pipelines, checks and deploys
- A push lists its first commit messages and links to the comparison
- Durations are shown as
2m 10sand states as plain words (opened, passed, failed) - The how-to pages show the messages as text
Fixed
- Failed Netlify deploys show the error message
watchis no longer shown as a star, and "1 commit" is in the singular- Automatic Netlify deploys no longer say "Triggered by Netlify Console"
- The links to GitLab pipelines and jobs work
- Wiki and vulnerability states are shown in words
1.12.1
Fixed
- Bug fixes and improvements
1.12.0
Added
- A button in the
/startand/rotate confirmmessages copies the secret key with one tap
Changed
- The bot answers a command once even when Telegram delivers it twice
- An empty line separates the secret key from the text below it in the
/startmessage
1.11.0
Changed
- The
/startmessage labels each endpoint by service, hides the secret key as a spoiler, shows the generic example on several lines with a placeholder instead of the real key, and has Guide and Policies buttons - The message of
/rotate confirmhides the new key as a spoiler too
1.10.1
Fixed
- Bug fixes and improvements
1.10.0
Fixed
- Bug fixes and improvements
1.9.0
Fixed
- Bug fixes and improvements
1.8.0
Fixed
- Bug fixes and improvements
1.7.0
Changed
- Messages are counted per month and service, not when they were sent. The policies describe it
1.6.1
Fixed
- Webhook URLs work with a trailing slash or a query string, and invalid ones answer
404right away
1.6.0
Added
/rotateand/rotate confirmgenerate a new secret key for the chat. The webhook URLs do not change
Security
- In groups only administrators can use
/startand/rotate, other members no longer see the endpoints and the secret
Fixed
- Two
/startsent at the same time could create two hooks for the same chat
1.5.0
Fixed
- Titles, branch names, usernames and form fields with
_,*, backticks or[no longer break the formatting of the message - Events with missing or unexpected fields produce a readable message instead of being dropped, missing values are shown as
-
1.4.3
Security
- The generic and GitLab secrets are compared in a way that does not leak information
- Netlify requests must be signed with the JWS secret token, and the signature checks of GitHub and Netlify can no longer be turned off
1.4.2
Security
- The bot only accepts requests that really come from Telegram
1.4.1
Changed
- New toucan icon and a new image for the previews of the site
1.4.0
Added
- Documentation of the generic hook: accepted formats and examples for GitHub Actions and Node.js
Changed
- The site was redesigned: a quick start and one page per service
Fixed
- The generic hook accepts
text/plain, JSON strings,{"text": "..."}and any JSON, and answers 400 to an empty body - Markdown that Telegram cannot parse is sent again as plain text instead of being lost
1.3.0
Changed
- The site was rebuilt, with the same URLs and an automatic dark and light theme
1.2.0
Fixed
- The GitHub hook counted its messages as GitLab ones and used the GitLab message for pushes
- The GitHub signature is checked correctly
- Hook requests finish before the answer is sent, and the bot always replies
1.1.0
Fixed
- Bug fixes and improvements
1.0.0
Added
- First release