ZEVA2 - BC now on permanent DST
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 6
- Avg merge
- 14h 22m
- Merged PRs (30d)
- 32
Description
**Describe the task**
The zeva2 app relies on the underlying node image's bundled IANA time zone database to be able to do time/date operations correctly (e.g. convert 2026-11-15T08:00:00Z correctly to 2026-11-15T01:00:00 PDT instead of 2026-11-15T00:00:00 PST).
The current time zone database version is 2026a (https://www.iana.org/time-zones), and does not yet reflect BC's switch to permanent DST; when a version that does reflect this change is published and included in a stable version of node, we should upgrade to that version.
**Purpose**
Timestamps stored in the database are in GMT; the app needs an up-to-date IANA tzdb to be able to convert these times correctly to BC time. The good news is that even if we do not update in time (i.e. before the first Sunday of November 2026), the timestamps will still be technically correct. That is, if on 2026-11-15T14:00 PDT (the correct BC time), a history action occurs, it will be displayed as having occurred on 2026-11-15T13:00 PST and saved as 2026-11-15T21:00:00 GMT in the db. When we do update the tzdb, that GMT time will be interpreted correctly as 2026-11-15T14:00 PDT and displayed as such in the app.
**Acceptance Criteria**
(1) Keep on eye on the IANA tzdb and node versions.
(2) Upgrade zeva2 when they upgrade.
Contributor guide
No contributing guide indexed for this repository
Research direction
Monitor the IANA tzdb and stable Node releases for a version that includes BC's permanent-DST change. When available, locate zeva2's Node image or version configuration, upgrade it, and verify that 2026-11-15T08:00:00Z converts to 01:00 PDT rather than 00:00 PST.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100