-
-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Update moment-timezone dependency #10870
Comments
refs TryGhost/Ghost#10870 - Reverts moment timezone to `0.5.23`
refs #10870 - Reverts moment-timezone version in url-utils to 0.5.23 to fix moment format issue
Pulled down and attempted a version bump to
|
I open a PR for it plz take a look if it can resolve the issue for not ? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
issue TryGhost#10870 The cause of the problem: there were 2 installations of moment-timezone. And moment-timezone overrides updateOffset function of moment. And the moment was calling the wrong one because there were 2 of them. I fixed yarn.lock to install only one of them.
refs TryGhost/Ghost#10870 - Reverts moment timezone to `0.5.23`
refs TryGhost/Ghost#10870 - Reverts moment timezone to `0.5.23`
refs TryGhost/Ghost#10870 - Reverts moment timezone to `0.5.23`
We're going to switch to luxon instead, see #13648 |
Context
After Renovate bumped moment-timezone to
0.5.25
from0.5.23
one of the regression tests started failing. The reason test failed, was a change informat()
output for this assertion. The format was using local timezone instead of globally set 'UTC' one. The version in which the behavior change was introduced in moment-timezone 0.5.24. Was unable to pin down/replicate the issue in a clean environment. Added description of initial findings mentioned in the issue ofmoment-timezone
repository.TODO
The version bump will be reverted for now and added to ignore list in Renovate until the original issue is better understood. For someone who picks this issue up should make sure:
moment-timezone
package version to the latest in coremoment-timezone
package version in SDK(Revert TryGhost/SDK@5f0fc04)
moment-timezone
from Renovate ignore listNOTE: When updating to a newer version please pay attention to performance changes as
moment
is known to be one of the main perf. bottlenecks in Ghost.The text was updated successfully, but these errors were encountered: