-
1.2.1 Stable
released this
2024-08-20 11:50:19 +00:00 | 0 commits to main since this releaseThis bot connects your team to the outside and makes it addressable. Install it on a device which is always online so it can forward messages between your team and the outside. It needs the credentials to your team's public e-mail address.
Release Notes
Nothing to worry, you can just upgrade.
What's Changed
- fix: offboarding: remove ppl only from groups they were part of
- Mark messages as read after someone talked about it in a relay group
Downloads
-
1.2.0 Stable
released this
2024-08-20 10:27:42 +00:00 | 3 commits to main since this releaseThis bot connects your team to the outside and makes it addressable. Install it on a device which is always online so it can forward messages between your team and the outside. It needs the credentials to your team's public e-mail address.
Release Notes
Nothing to worry, you can just upgrade.
What's Changed
- check if it's a relay group in pickle instead of guessing
- offboarding: remove ex-admins from relay groups
Full Changelog: https://github.com/deltachat-bot/team-bot/compare/1.1.0...1.2.0
Downloads
-
1.1.0 Stable
released this
2024-04-30 09:27:22 +00:00 | 7 commits to main since this releaseThis bot connects your team to the outside and makes it addressable. Install it on a device which is always online so it can forward messages between your team and the outside. It needs the credentials to your team's public e-mail address.
Release Notes
Nothing to worry about while upgrading.
Changes
- New
/generate-invite
command to get aOPENPGP4FPR
invite code, so users can establish guaranteed end-to-end encryption with the bot - Removed logging of incoming messages
Downloads
- New
-
1.0.0 Stable
released this
2024-04-03 12:52:23 +00:00 | 15 commits to main since this releaseThis bot connects your team to the outside and makes it addressable. Install it on a device which is always online so it can forward messages between your team and the outside. It needs the credentials to your team's public e-mail address.
Release Notes
Renamed repository from teams-bot to team-bot
if you have set up the bot before the renaming from teams-bot to team-bot, you might need to fix some paths during the upgrade.
If you are using a pyinfra deployment based on pyinfra.py:
- the
deploy_teams_bot
function was renamed todeploy_team_bot
, you need to rename that in your deploy.py as well - pass
dbdir=
todeploy_team_bot
to keep using your existent delta chat database directory - stop and disable the
teams-bot.service
- start the new
team-bot.service
withsystemctl --user enable --now team-bot
Now exactly one systemd service should be running.
If you are using a different way to deploy the team-bot, you can take this as an orientation.
Downloads
- the