Skip to content

fix: pin cron jobs to UTC - #96

Merged
vycdev merged 1 commit into
vycdev:developfrom
vycdev2:fix/quartz-cron-utc
Aug 10, 2026
Merged

fix: pin cron jobs to UTC#96
vycdev merged 1 commit into
vycdev:developfrom
vycdev2:fix/quartz-cron-utc

Conversation

@vycdev2

@vycdev2 vycdev2 commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Pin every Quartz cron schedule to UTC so host timezone changes cannot shift daily bot avatar, honeypot rename, UBI, or wealth-tax execution times.
  • Add a regression test that resolves each configured cron trigger and verifies its timezone.

Verification

  • dotnet build — passed: 0 errors; 2 existing NU1903 dependency warnings.
  • dotnet test --no-build --filter 'FullyQualifiedName~BotStartupExtensionsTests' --logger 'console;verbosity=minimal' — passed: 1/1.
  • dotnet test --no-build --logger 'console;verbosity=minimal' — 298 passed, 2 failed: the same pre-existing tr-TR culture cases fail on synced develop because this runner uses globalization-invariant mode.
  • git diff --check upstream/develop...HEAD — passed.

Risk

  • Low — this makes existing cron expressions deterministic across deployment hosts without changing their documented clock times.

This was generated by an AI agent (vycdev2). Please verify any changes before merging or applying.

@vycdev
vycdev merged commit 941f2f8 into vycdev:develop Aug 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants