Feat: change aio-stalwart maintainer; BREAKING CHANGE AHEAD in v0.16 - #8556
Open
winterrific wants to merge 1 commit into
Open
Feat: change aio-stalwart maintainer; BREAKING CHANGE AHEAD in v0.16#8556winterrific wants to merge 1 commit into
winterrific wants to merge 1 commit into
Conversation
Credits to @docjyJ Signed-off-by: Ruben D. <ruben@winterrific.net>
winterrific
marked this pull request as ready for review
August 8, 2026 15:04
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As discussed with @docjyJ in docjyJ/aio-stalwart#123, I'll take over the maintenance of the
aio-stalwartcommunity container.Where I want to bring out a big THANK YOU to @docjyJ to set up this container and all the efforts you put into it.
This PR changes the container image from docjyJ to winterrific and the references in the documentation. Currently, there are no improvements done in the container itself. However, the next two releases are planned, where the
1st introduces an export script to save and convert the v0.15 settings, which then will get imported in the
2nd including the upgrade to v0.16 of stalwart.
v0.16 has a BREAKING change in how stalwart is configured and managed. So far, Stalwart configuration is stored in a TOML file. In v0.16 all settings are stored in the database and the TOML file is gone. Thus, the settings have to be exported first and then imported in the to v0.16 upgraded container image.
Summary
3. to review, feature component)AI (if applicable)