openchronology-migrate starts the enabled mail worker again after an upgrade (#371)
- github
- github/openchronology/timeline-app
- commit
- main
- github/athanclark
An upgrade of the Debian and RPM packages stops the server and the mail worker, but openchronology-migrate restarted only the server, so account email waited in the outbox until someone started the worker by hand. It now restarts openchronology-mail.service when it is enabled, and says so; a disabled worker (email not configured) stays stopped, and --no-restart still restarts nothing. postinst and openchronology-setup do the same where they start the server. The FreeBSD package (whose upgrade stops openchronology_mail too) restarts it when it is enabled; Homebrew restarts the mail agent when it is started, so it runs the new version; Windows' openchronology-migrate restarts OpenChronologyMail when it starts with Windows (the installer already did). The Debian and RPM tests enable the worker before the upgrade, with a stand-in systemctl in their systemd-less containers, and check that the upgrade stops it, openchronology-migrate starts it, and --no-restart or a disabled worker leaves it stopped. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/commit/139719ff4383a6184e06e50694056bcdcfd65d25