Fix Forgejo runner timezone (UTC -> America/Los_Angeles) #159

Merged
eblume merged 1 commit from fix-runner-timezone into main 2026-02-11 16:53:42 -08:00
Owner

Summary

  • Set TZ=America/Los_Angeles on the Forgejo runner container

The runner pod defaults to UTC. When releases are cut in the evening PST, towncrier stamps changelog entries with tomorrow's date (e.g., v1.6.2 shows 2026-02-12 despite being released on the evening of Feb 11 PST).

Deployment

After merge, sync the forgejo-runner ArgoCD app:

argocd app sync forgejo-runner

The runner pod will restart with the new timezone. Note: the v1.6.2 changelog entry will remain dated 2026-02-12; future entries will use PST dates, so dates may appear non-sequential once.

## Summary - Set `TZ=America/Los_Angeles` on the Forgejo runner container The runner pod defaults to UTC. When releases are cut in the evening PST, towncrier stamps changelog entries with tomorrow's date (e.g., v1.6.2 shows 2026-02-12 despite being released on the evening of Feb 11 PST). ## Deployment After merge, sync the forgejo-runner ArgoCD app: ``` argocd app sync forgejo-runner ``` The runner pod will restart with the new timezone. Note: the v1.6.2 changelog entry will remain dated 2026-02-12; future entries will use PST dates, so dates may appear non-sequential once.
The runner pod defaulted to UTC, causing towncrier to stamp changelog
entries with tomorrow's date when releases were cut in the evening PST.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
eblume merged commit 42ebc2b122 into main 2026-02-11 16:53:42 -08:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
eblume/blumeops!159
No description provided.