Repository navigation
TenantService v2.0.11
What's Changed (since v2.0.10)
- Send tenant SMTP test mail to verified admin address by @Storypapst in #291
- Allow approved notification purposes in tenant OWN relay by @Storypapst in #280
- Relay invites and DPA mails through the Träger's own mail server by @Storypapst in #298
- Relay the planned maintenance notice through an organisation's own mail server by @Storypapst in #299
- Require explicit confirmation for unusual tenant SMTP transport by @Storypapst in #290
- docs(agents): rules for issue and PR writing, and whose text may be edited by @Storypapst in #265
- fix(branding): inherit the platform logo from the single-domain main tenant by @Storypapst in #301
- Expose the stored contract confirmation language by @Storypapst in #303
- Keep OWN reply-mail correlation in the MIME header by @Storypapst in #287
- Persist assistant appearance and inherited notification channel policies by @Storypapst in #304
- Allow self-help appointment purposes in tenant relay by @Storypapst in #292
Full Changelog: v2.0.10...v2.0.11
Reviewed release summary — v2.0.11
Organisations can test their saved mail server by sending to the signed-in admin's verified address. Their own mail server can relay approved counselling notifications, invitations, contract messages, planned-maintenance notices and self-help appointment messages. Unusual mail-server settings require explicit confirmation. Delivery references are carried in email headers. Platform-logo inheritance is corrected, contract confirmations expose the chosen language, and assistant appearance and inherited conversation-channel settings are saved.
The appointment relay is included; sender activation and received-message acceptance remain separate. The planned-maintenance notice follows the optional notification switch; the separate mandatory outage notice is outside this delivery.
The team reported manual testing. Included source changes, internal QA on Dev/Stage and external acceptance are separate states. Missing agent test evidence does not make merged implementation unfinished.
Received mail, organisation-specific delivery and deployed channel-policy behaviour require their own acceptance evidence. This source list does not establish that every relay purpose or language has been accepted on Dev.
Included source changes and GitHub references
The list below records PR commits included in this repository’s published v2.0.11 source tag and absent from v2.0.10. It includes release bookkeeping where present. Links are explicit issue or PR references, not automatic closure or whole-ticket completion claims.
For developers — source inclusion evidence:
Previous source tag: v2.0.10
Published source tag: v2.0.11
Included PR merge commits: 12
Compared source commits: 57 of 57
Each listed PR merge commit occurs in the GitHub tag comparison.
Deployment, worker activation, received mail and external acceptance are separate checks.