notify-bridge/RELEASE_NOTES.md

v0.3.2 (2026-04-22)

Scheduler now honors the app-level timezone. Before this, a cron expression like 0 9 * * * was firing at 09:00 in the server's host-local tz — not at 09:00 in the timezone the admin configured under Settings — because CronTrigger.from_crontab was constructed without a tz. Same fix extends to scheduler-provider template rendering so {{ current_date }} / {{ current_time }} match the configured tz, and scheduled firings now show up in the dashboard event feed with context.

Bug Fixes

• Cron triggers honor app timezone — all tracker and action cron triggers are now built with the configured app tz; CronTrigger freezes its tz at construction, so the PUT /settings endpoint rebuilds existing cron jobs when the timezone changes. Scheduled messages that were silently firing at host-local time will fire at the intended time after upgrade. (1024085)
• Scheduler template context renders in the app tz — current_date, current_time, current_datetime, current_weekday in scheduler-provider templates are now formatted in the configured timezone instead of UTC/host-local. Custom templates that built date strings in the wrong tz now render correctly. (1024085)

Features

• New timezone template variable — scheduler-provider templates can reference {{ timezone }} to display the active IANA tz alongside a date/time. Added across the context builder, variable catalog, sample context, and runtime validator (per the project's 6-file sync rule for template vars). (1024085)
• scheduled_message events surface in the dashboard feed — EventLog entries for scheduled firings now carry schedule_type, cron_expression / interval_seconds, timezone, and fire_count; the dashboard renders them with a dedicated label, icon, and colour so operators can see at a glance when scheduled messages actually fired. (1024085)

---

All Commits

• 1024085 — fix(scheduler): honor app timezone for cron triggers and log scheduled events (alexei.dolgolyov)