[Snyk] Upgrade moment-timezone from 0.5.34 to 0.5.46 #179
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.
Snyk has created this PR to upgrade moment-timezone from 0.5.34 to 0.5.46.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 12 versions ahead of your current version.
The recommended version was released on a month ago.
Issues fixed by the recommended upgrade:
SNYK-JS-MOMENT-2440688
SNYK-JS-MOMENT-2944238
Release notes
Package name: moment-timezone
2024b
. This only affects historical timestamps; no future timestamps have changed.2024a
.2023d
..valueOf()
to returnNaN
for invalid zoned objects (matching defaultmoment
) #1082.tz.guess()
.getZone()
calls in.tz()
.2023c
2023b
moment
npm dependency to2.29.4
to remove automated warnings about insecure dependencies #1004.Moment Timezone still works with core Moment
2.9.0
and higher.moment-timezone-with-data-2012-2022
bundles #1035.Use the rolling
moment-timezone-with-data-10-year-range
files instead.2022g
2022f
2022e
moment.tz.dataVersion
property to TypeScript definitions #930.tar.gz
files from npm releases #1000Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: