Skip to content

Migration guide

Migrating from v0.18 to v0.19

Invite links have been replaced by join links, and the invite_code is no longer used. As part of this change, the guest_link_builder option in the [frontend] section has been removed.

If your configuration still sets guest_link_builder, the service keeps starting but logs an Unknown configuration key warning. Remove the option from your configuration to silence the warning:

[frontend]
#guest_link_builder = "{base_url}/invite/{invite_id}"

Migrating from v0.17 to v0.18

Environment variable prefix changed to OPENTALK_MAIL

The prefix used for configuration environment variables changed from MAILER to OPENTALK_MAIL, aligning the OpenTalk SMTP Mailer with the other OpenTalk services. Nested fields are still separated by two underscores __.

For example, the queue name is now set like this:

OPENTALK_MAIL_RABBIT_MQ__QUEUE_NAME=opentalk_mailer

The old MAILER prefix is still supported for backwards compatibility, so existing deployments keep working without changes. It is deprecated and should be replaced with the new prefix. If a setting is provided under both prefixes, the value from OPENTALK_MAIL takes precedence.

RabbitMQ queue is now durable and non-exclusive

The queue consumed by the SMTP Mailer is now declared as durable and non-exclusive so that tasks survive a broker restart.

If a queue with the configured name already exists on your broker with different properties (for example a non-durable queue from a previous version), RabbitMQ rejects the new declaration with a PRECONDITION_FAILED error and the service fails to start. In that case, delete the existing queue so it can be recreated with the new properties.