Update dependency tzinfo to v2 - autoclosed #192
Closed
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 PR contains the following updates:
"~> 1.2"
->"~> 2.0"
⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
tzinfo/tzinfo (tzinfo)
v2.0.6
Compare Source
Object#untaint
deprecation warnings on JRuby 9.4.0.0. #145.v2.0.5
Compare Source
DateTime
results to always use the proleptic Gregorian calendar.This affects
DateTime
results prior to 1582-10-15 and any arithmeticperformed on the results that would produce a secondary result prior to
1582-10-15.
either
TZInfo::DataSource#eager_load!
orTZInfo.eager_load!
. Compatiblewith Ruby On Rails'
eager_load_namespaces
. #129.v2.0.4
Compare Source
InvalidTimezoneIdentifier
exception raised when loading azoneinfo file that includes rules specifying an additional transition to the
final defined offset (for example, Africa/Casablanca in version 2018e of the
Time Zone Database). #123.
v2.0.3
Compare Source
default by zic version 2020b and later. The POSIX-style TZ string is now used
calculate DST transition times after the final defined transition in the file.
#120.
TimeWithOffset#getlocal
returning aTimeWithOffset
with thetimezone_offset
still assigned when called with an offset argument on JRuby9.3.
v2.0.2
Compare Source
v2.0.1
Compare Source
data with recent Ruby releases in safe mode. #100.
TZInfo::Timezone#=~
method that performs a regex match on the timezone identifier. #99.
TZInfo::Country#=~
method that performs a regex match on the countrycode.
v2.0.0
Compare Source
Added
to_local
andperiod_for
instance methods have been added toTZInfo::Timezone
. These are similar toutc_to_local
andperiod_for_utc
,but take the UTC offset of the given time into account.
abbreviation
,dst?
,base_utc_offset
andobserved_utc_offset
instancemethods have been added to
TZInfo::Timezone
, returning the abbreviation,whether daylight savings time is in effect and the UTC offset of the time zone
at a specified time.
TZInfo::Timestamp
class has been added. It can be used withTZInfo::Timezone
in place of aTime
orDateTime
.local_time
,local_datetime
andlocal_timestamp
instance methods havebeen added to
TZInfo::Timezone
. These methods construct localTime
,DateTime
andTZInfo::Timestamp
instances with the correct UTC offset andabbreviation for the time zone.
addition to support for version 1. The new version will remove the (no longer
needed)
DateTime
parameters from transition times, reduce memory consumptionand improve the efficiency of loading timezone and country indexes.
TZInfo::VERSION
constant has been added, indicating the TZInfo versionnumber.
Changed
or later mode) and Rubinius 3.
UTC). #49 and #52.
TimeWithOffset
,DateTimeWithOffset
orTZInfo::TimestampWithOffset
. These classes subclassTime
,DateTime
andTZInfo::Timestamp
respectively. They override thedefault behaviour of the base classes to return information about the observed
offset at the indicated time. For example, the zone abbreviation is returned
when using the
%Z
directive withstrftime
.transitions_up_to
,offsets_up_to
andstrftime
instance methods ofTZInfo::Timezone
now take the UTC offsets of given times into account(instead of ignoring them as was previously the case).
TZInfo::TimezonePeriod
class has been split into two subclasses:TZInfo::OffsetTimezonePeriod
andTZInfo::TransitionsTimezonePeriod
.TZInfo::OffsetTimezonePeriod
is returned for time zones that only have asingle offset.
TZInfo::TransitionsTimezonePeriod
is returned for periodsthat start or end with a transition.
TZInfo::TimezoneOffset#abbreviation
,TZInfo::TimezonePeriod#abbreviation
and
TZInfo::TimezonePeriod#zone_identifier
now return frozenString
instances instead of instances of
Symbol
.utc_offset
andutc_total_offset
attributes ofTZInfo::TimezonePeriod
and
TZInfo::TimezoneOffset
have been renamedbase_utc_offset
andobserved_utc_offset
respectively. The former names have been retained asaliases.
TZInfo::Timezone.get
,TZInfo::Timezone.get_proxy
andTZInfo::Country.get
can now be used with strings having any encoding. Previously, only encodings
that are directly comparable with UTF-8 were supported.
TZInfo::InvalidTimezoneIdentifier
exception messages.
TZInfo::InvalidCountryCode
exception messages.
files produced with version 2014c of the
zic
tool contain an initialtransition
2**63
seconds before the epoch. Zoneinfo files produced withversion 2014d or later of
zic
contain an initial transition2**59
secondsbefore the epoch. These transitions would previously have been ignored, but
are now returned in methods such as
TZInfo::Timezone#transitions_up_to
.TZInfo::RubyDataSource
andTZInfo::ZoneinfoDataSource
classes havebeen moved into a new
TZInfo::DataSources
module. Code that is settingTZInfo::ZoneinfoDataSource.search_path
orTZInfo::ZoneinfoDataSource.alternate_iso3166_tab_search_path
will need to beupdated accordingly.
TZInfo::InvalidZoneinfoDirectory
andTZInfo::ZoneinfoDirectoryNotFound
exception classes raised by
TZInfo::DataSources::ZoneinfoDataSource
havebeen moved into the
TZInfo::DataSources
module.:ruby
or instantiatingTZInfo::DataSources::RubyDataSource
will now immediately raise aTZInfo::DataSources::TZInfoDataNotFound
exception ifrequire 'tzinfo/data'
fails. Previously, a failure would only occur later when accessing an index or
loading a timezone or country.
DEFAULT_SEARCH_PATH
andDEFAULT_ALTERNATE_ISO3166_TAB_SEARCH_PATH
constants of
TZInfo::DataSources::ZoneinfoDataSource
have been made private.TZInfo::Country.data_source
,TZInfo::DataSource.create_default_data_source
,TZInfo::DataSources::ZoneinfoDataSource.process_search_path
,TZInfo::Timezone.get_proxies
andTZInfo::Timezone.data_source
methods havebeen made private.
improved.
String
instances when loadingcountry and time zone data.
by concurrent-ruby.
TZInfo::DataSource
implementations have been moved into theTZInfo::DataSources
module.TZInfo::TransitionDataTimezoneInfo
class has been removed and replacedwith
TZInfo::DataSources::TransitionsDataTimezoneInfo
andTZInfo::DataSources::ConstantOffsetDataTimezoneInfo
.TZInfo::DataSources::TransitionsDataTimezoneInfo
is constructed with anArray
ofTZInfo::TimezoneTransition
instances representing times when theoffset changes.
TZInfo::DataSources::ConstantOffsetDataTimezoneInfo
isconstructed with a
TZInfo::TimezoneOffset
instance representing the offsetconstantly observed in a time zone.
TZInfo::DataSource#timezone_identifiers
method should no longer beoverridden in custom data source implementations. The implementation in the
base class now calculates a result from
TZInfo::DataSource#data_timezone_identifiers
andTZInfo::DataSource#linked_timezone_identifiers
.TZInfo::DataSources::RubyDataSource
to_s
andinspect
methods now include the time zone database and tzinfo-data versions.
Removed
TZInfo::Timezone
that accept time arguments no longer allowInteger
timestamp values.Time
,DateTime
orTZInfo::Timestamp
valuesor objects that respond to
to_i
,subsec
and optionallyutc_offset
mustbe used instead.
%:::z
format directive can now only be used withTZInfo::Timezone#strftime
if it is supported byTime#strftime
on theruntime platform.
TZInfo::Timezone.new(identifier)
andTZInfo::Country.new(code)
toobtain a specific
TZInfo::Timezone
orTZInfo::Country
will no longer work.TZInfo::Timezone.get(identifier)
andTZInfo::Country.get(code)
should beused instead.
TZInfo::TimeOrDateTime
class has been removed.valid_for_utc?
,utc_after_start?
,utc_before_end?
,valid_for_local?
,local_after_start?
andlocal_before_end?
instancemethods of
TZInfo::TimezonePeriod
have been removed. Comparisons can beperformed with the results of the
starts_at
,ends_at
,local_starts_at
and
local_ends_at
methods instead.to_local
andto_utc
instance methods ofTZInfo::TimezonePeriod
andTZInfo::TimezoneOffset
have been removed. Conversions should be performedusing the
TZInfo::Timezone
class instead.TZInfo::TimezonePeriod#utc_total_offset_rational
method has beenremoved. Equivalent information can be obtained using the
TZInfo::TimezonePeriod#observed_utc_offset
method.datetime
,time
,local_end
,local_end_time
,local_start
andlocal_start_time
instance methods ofTZInfo::TimezoneTransition
have beenremoved. The
at
,local_end_at
andlocal_start_at
methods should be usedinstead and the result (a
TZInfo::TimestampWithOffset
) converted to either aDateTime
orTime
by callingto_datetime
orto_time
on the result.us_zones
andus_zone_identifiers
class methods ofTZInfo::Timezone
have been removed.
TZInfo::Country.get('US').zones
andTZInfo::Country.get('US').zone_identifiers
should be used instead.v1.2.11
Compare Source
Object#untaint
deprecation warnings on JRuby 9.4.0.0. #145.v1.2.10
Compare Source
loaded with
require
when used withRubyDataSource
. Please refer toGHSA-5cm2-9h8c-rvfx for
details. CVE-2022-31163.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.