0.9.2

0.9.2

Fixed

• Backup schedules now run in the container's timezone — the scheduler was hardcoded to UTC, so a job entered as "midnight" fired at midnight UTC rather than local wall-clock time, and cron times appeared shifted in the UI. The timezone is now resolved from the container's TZ env var (falling back to the host's local zone, then UTC) and applied to every trigger; the resolved zone is logged at startup.
• Numeric cron weekdays now map to the correct days — APScheduler's from_crontab interprets numeric day-of-week as 0=Monday, whereas standard crontab uses 0/7=Sunday, 1=Monday. As a result an expression like 0 0 * * 1,3,5 (intended Mon/Wed/Fri) actually fired Tue/Thu/Sat. Numeric weekdays are now translated correctly, preserving ranges (1-5) and steps (1-5/2); named forms (mon-fri) were already correct and are unchanged. Existing saved schedules pick up the fix automatically on restart.

Changed

• Cron validation and scheduling now share a single parser (make_cron_trigger in validation.py), so any expression that passes validation can always be scheduled. As a side effect, standard crontab 7 for Sunday is now accepted where it was previously rejected.