Skip to content

deps: update timezone to 2022f#4

Closed
github-actions[bot] wants to merge 3 commits into
mainfrom
test/add-a-test-to-ensure-the-correctness-of-timezone-upgrades
Closed

deps: update timezone to 2022f#4
github-actions[bot] wants to merge 3 commits into
mainfrom
test/add-a-test-to-ensure-the-correctness-of-timezone-upgrades

Conversation

@github-actions
Copy link
Copy Markdown

@github-actions github-actions Bot commented Nov 3, 2022

This PR was generated by tools/timezone-update.yml.

Updates the ICU files as per the instructions present in https://github.com/nodejs/node/blob/main/doc/contributing/maintaining-icu.md#time-zone-data

To test, build node off this branch & log the version of tz using

console.log(process.versions.tz)
RaisinTen and others added 3 commits November 3, 2022 18:02
Currently, there's no way to know if a timezone upgrade PR is correct
without building and testing the change locally. This change provides a
solution for that.

Signed-off-by: Darshan Sen <raisinten@gmail.com>
Signed-off-by: Darshan Sen <raisinten@gmail.com>
@RaisinTen RaisinTen closed this Nov 3, 2022
RaisinTen added a commit that referenced this pull request Nov 3, 2022
Currently, there's no way to know if a timezone upgrade PR is correct
without building and testing the change locally. This change provides a
solution for that.

Tested in #4.

Signed-off-by: Darshan Sen <raisinten@gmail.com>
nodejs-github-bot pushed a commit to nodejs/node that referenced this pull request Nov 10, 2022
Currently, there's no way to know if a timezone upgrade PR is correct
without building and testing the change locally. This change provides a
solution for that.

Tested in RaisinTen#4.

Signed-off-by: Darshan Sen <raisinten@gmail.com>
PR-URL: #45299
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
richardlau pushed a commit to richardlau/node-1 that referenced this pull request Nov 19, 2022
Currently, there's no way to know if a timezone upgrade PR is correct
without building and testing the change locally. This change provides a
solution for that.

Tested in RaisinTen#4.

Signed-off-by: Darshan Sen <raisinten@gmail.com>
PR-URL: nodejs#45299
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
richardlau pushed a commit to richardlau/node-1 that referenced this pull request Nov 19, 2022
Currently, there's no way to know if a timezone upgrade PR is correct
without building and testing the change locally. This change provides a
solution for that.

Tested in RaisinTen#4.

Signed-off-by: Darshan Sen <raisinten@gmail.com>
PR-URL: nodejs#45299
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
ruyadorno pushed a commit to nodejs/node that referenced this pull request Nov 21, 2022
Currently, there's no way to know if a timezone upgrade PR is correct
without building and testing the change locally. This change provides a
solution for that.

Tested in RaisinTen#4.

Signed-off-by: Darshan Sen <raisinten@gmail.com>
PR-URL: #45299
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
richardlau pushed a commit to nodejs/node that referenced this pull request Nov 23, 2022
Currently, there's no way to know if a timezone upgrade PR is correct
without building and testing the change locally. This change provides a
solution for that.

Tested in RaisinTen#4.

Signed-off-by: Darshan Sen <raisinten@gmail.com>
PR-URL: #45299
Backport-PR-URL: #45521
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Fixes: #45276
targos pushed a commit to nodejs/node that referenced this pull request Nov 24, 2022
Currently, there's no way to know if a timezone upgrade PR is correct
without building and testing the change locally. This change provides a
solution for that.

Tested in RaisinTen#4.

Signed-off-by: Darshan Sen <raisinten@gmail.com>
PR-URL: #45299
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
richardlau pushed a commit to nodejs/node that referenced this pull request Nov 24, 2022
Currently, there's no way to know if a timezone upgrade PR is correct
without building and testing the change locally. This change provides a
solution for that.

Tested in RaisinTen#4.

Signed-off-by: Darshan Sen <raisinten@gmail.com>
PR-URL: #45299
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
guangwong pushed a commit to noslate-project/node that referenced this pull request Jan 3, 2023
Currently, there's no way to know if a timezone upgrade PR is correct
without building and testing the change locally. This change provides a
solution for that.

Tested in RaisinTen/node#4.

Signed-off-by: Darshan Sen <raisinten@gmail.com>
PR-URL: nodejs/node#45299
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
guangwong pushed a commit to noslate-project/node that referenced this pull request Jan 3, 2023
Currently, there's no way to know if a timezone upgrade PR is correct
without building and testing the change locally. This change provides a
solution for that.

Tested in RaisinTen/node#4.

Signed-off-by: Darshan Sen <raisinten@gmail.com>
PR-URL: nodejs/node#45299
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
danielleadams pushed a commit to nodejs/node that referenced this pull request Jan 3, 2023
Currently, there's no way to know if a timezone upgrade PR is correct
without building and testing the change locally. This change provides a
solution for that.

Tested in RaisinTen#4.

Signed-off-by: Darshan Sen <raisinten@gmail.com>
PR-URL: #45299
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

2 participants