1.2.1

This 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 by @missytake in #17
• Mark messages as read after someone talked about it in a relay group by @missytake in #18

Full Changelog: 1.2.0...1.2.1

1.2.0

This 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 by @missytake in #13
• offboarding: remove ex-admins from relay groups by @missytake in #14

Full Changelog: 1.1.0...1.2.0

1.1.0

This 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 a OPENPGP4FPR invite code, so users can establish guaranteed end-to-end encryption with the bot
• Removed logging of incoming messages

1.0.0

This 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 to deploy_team_bot, you need to rename that in your deploy.py as well
• pass dbdir= to deploy_team_bot to keep using your existent delta chat database directory
• stop and disable the teams-bot.service
• start the new team-bot.service with systemctl --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.