-
Notifications
You must be signed in to change notification settings - Fork 958
chore: update to node 20.19.4 #19188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
ea6c4b1
update node
aslilac d2f4a58
update in ci
aslilac 7f654f6
Merge branch 'main' into lilac/node-20.19
aslilac b6273be
bump
aslilac fcc2af1
Merge branch 'main' into lilac/node-20.19
aslilac def2ebe
lints
aslilac 66bafa3
timezone weirdness abounds
aslilac File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,22 @@ | ||
/** | ||
* Ideally the version of tzdata should correspond to the version of the | ||
* timezone database used by the version of Node we're running our tests | ||
* against. For example, Node v20.19.4 and tzdata@1.0.44 both correspond to | ||
* version 2025b of the ICU timezone: | ||
* https://github.com/nodejs/node/blob/v20.19.4/test/fixtures/tz-version.txt | ||
* https://github.com/rogierschouten/tzdata-generate/releases/tag/v1.0.44 | ||
* | ||
* For some reason though, the timezones allowed by `Intl.DateTimeFormat` in | ||
* Node diverged slightly from the timezones present in the tzdata package, | ||
* despite being derived from the same data. Notably, the timezones that we | ||
* filter out below are not allowed by Node as of v20.18.1 and onward–which is | ||
* the version that updated the 20 release line from 2024a to 2024b. | ||
*/ | ||
import tzData from "tzdata"; | ||
|
||
export const timeZones = Object.keys(tzData.zones).sort(); | ||
export const timeZones = Object.keys(tzData.zones) | ||
.filter((it) => it !== "Factory" && it !== "null") | ||
.sort(); | ||
|
||
export const getPreferredTimezone = () => | ||
Intl.DateTimeFormat().resolvedOptions().timeZone; |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍