Update tzdata to ~> 1.1 to Fix Handling of Timezone Database #43
Conversation
This file contains 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
|
The changes look good to me, CI might be failing due to |
|
Sounds good @ananthakumaran 👌 |
|
Could we give it a new tag also @ananthakumaran :) |
|
done |
|
Awesome dude. Thanks for the help. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 pull request updates the tzdata version to ~> 1.1 to resolve the issue with loading the timezone database in certain deployment environments, as described in tzdata issue #148.
Updating tzdata to 1.1.2 addresses cases where the timezone database is not properly loaded on the first deploy due to missing ETS tables. This version ensures better handling of database loading in production environments.
Additionally, the mix.lock file has been updated to reflect the changes in dependencies.