Consider Using Timezones For Workflows With Scheduling

[O957]

GitHub actions supports timezones now (https://github.blog/changelog/2026-03-19-github-actions-late-march-2026-updates/#github-actions-timezone-support-for-scheduled-workflows).

At present, the following workflows are setup as:

• cache-deps.yaml : cron: "10 16 * * *"
• archive_target_data.yml : cron: "20 17 * * 3"
• cache-hubval-deps.yaml : cron: "10 0 * * *"

GitHub Actions cron schedules without timezone run in UTC. Daylight savings time (DST) can shift when the actions are ran, if they're not pinned to a timezone.

E.g. the intent for create-ensemble is to run it at 8:30 AM Eastern (the cron is set to 30 13 * * 4 (1:30 PM UTC), which is 8:30 AM EST) but during DST, 1:30 PM UTC is actually 9:30 AM EDT, an hour later.

Adding timezone: "America/New_York" would alleviate this issue.

Example:

- cron: "10 16 * * *"
  timezone: "America/New_York"