Repository navigation
fix: keep Automation schedules and run history in local time - #2091
Open
Douglasymlai wants to merge 5 commits into
Open
Douglasymlai wants to merge 5 commits into
Douglasymlai wants to merge 5 commits into
Conversation
Douglasymlai
marked this pull request as ready for review
October 22, 2026 21:48
# Conflicts: # src/components/Trigger/TriggerDialog.tsx
This branch has not been deployed
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.
Pull Request
Related Issue
N/A — maintainer-directed repair; no linked issue required for this PR.
Description
Automation schedules saved today’s UTC offset and could shift at daylight-saving changes. New schedules use local cron fields plus an IANA zone when supported. Verify the echoed zone and fall back to the UTC contract when it was not persisted. Previews use the saved zone, and offset-free server timestamps parse as UTC. Existing schedules without a zone keep their UTC contract on edit. The self-hosted scheduler uses additive timezone, date and expiration rules.
Current main is merged, retaining Automation draft review/focus behavior.
Testing Evidence (REQUIRED)
116 focused frontend tests and 9 self-hosted scheduler tests passed, including London/New York DST changes, missing/repeated local hours, UTC fallback, persisted zones and editing legacy schedules on a timezone-capable server. Type-check, focused ESLint/Prettier and git diff --check passed. Existing SchedulePicker/shared primitives and semantic tokens retained. No full packaged-app time-zone/theme matrix was run. The matching production server change must be deployed before this is released.
Automated checks only; manual app testing is pending.
What is the purpose of this pull request?
Contribution Guidelines Acknowledgement