I'm the maintainer of the tzinfo gem. et-orbi currently depends on tzinfo with open-ended version constraints.
I'm working on a new major release of tzinfo (v2.0.0), which I hope to release sometime in the coming months. This will break backwards compatibility in a few ways that affect et-orbi:
The TimezonePeriod#to_local and TimezonePeriod#to_utc methods have been removed. Timezone#utc_to_local and Timezone#local_to_utc should be used instead.
TZInfo::TransitionDataTimezoneInfo has been replaced with TZInfo::DataSources::ConstantOffsetDataTimezoneInfo and TZInfo::DataSources::TransitionsDataTimezoneInfo.
Methods that return local times (such as Timezone#utc_to_local) now return results using the appropriate local UTC offset instead of always using UTC.
This pull request includes changes that make et-orbi compatible with both the upcoming tzinfo v2.0.0 release and existing tzinfo releases.
To test with the current development version of tzinfo instead of a released version, you can add the following line to the Gemfile:
I'm the maintainer of the tzinfo gem. et-orbi currently depends on tzinfo with open-ended version constraints.
I'm working on a new major release of tzinfo (v2.0.0), which I hope to release sometime in the coming months. This will break backwards compatibility in a few ways that affect et-orbi:
TimezonePeriod#to_local
andTimezonePeriod#to_utc
methods have been removed.Timezone#utc_to_local
andTimezone#local_to_utc
should be used instead.TZInfo::TransitionDataTimezoneInfo
has been replaced withTZInfo::DataSources::ConstantOffsetDataTimezoneInfo
andTZInfo::DataSources::TransitionsDataTimezoneInfo
.Timezone#utc_to_local
) now return results using the appropriate local UTC offset instead of always using UTC.This pull request includes changes that make et-orbi compatible with both the upcoming tzinfo v2.0.0 release and existing tzinfo releases.
To test with the current development version of tzinfo instead of a released version, you can add the following line to the
Gemfile
: