fix(timezone): recompute offset on init to handle DST transitions glo… #2962
Conversation
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
1 participant
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.
This update fixes DST-related inconsistencies in the Day.js timezone plugin.
Previously, timezone offsets were not recalculated when Dayjs instances were reinitialized through methods like .add(), .set(), or .startOf(), causing 1-hour drifts around DST transitions.
Fix:
Patched the private init() method to recompute the timezone offset whenever $x.$timezone is present:
Ensures accurate offsets across all time manipulation methods.
Prevents DST-related time shifts.
Keeps full backward compatibility.
Result:
DST offsets now remain correct for timezone-aware instances across all operations.
All 93 test suites pass successfully.
Linked Issue
#2957