view release on metacpan or  search on metacpan

CHANGES  view on Meta::CPAN

      precaution.

    [Bug fixes]
    - Hardened _parse_timestamp() to drop the formatter when an installed
      DateTime::Format::JP is older than v0.1.7. Older versions only know how to format
      DateTime objects and emit a warning under an unregistered category when given a
      DateTime::Lite, which broke tests using warnings::register on CPAN Testers smokers.
      Stringification now falls back to DateTime::Lite's iso8601() in that case.
    - Bumped the minimum required version of DateTime::Format::Lite from v0.1.2 to v0.1.3.
      Version v0.1.2 called DateTime::Lite::TimeZone->new() without the extended option
      when resolving the %O token, which made timezone abbreviations such as JST or CET
      fail to resolve via the extended_aliases table. v0.1.3 fixes this by passing extended => 1.
    - Module::Generic::Global: callers of _share_repo() now propagate its return value,
      returning early with a type-appropriate value if the shared repository cannot be
      initialised (typically during END or DESTRUCT phases). This eliminates "Invalid
      value for shared scalar (in cleanup)" warnings that were emitted when methods such
      as remove(), set(), or get() drilled into $REPO->{ $ns } after threads::shared had
      begun tearing down its structures.
    - Fixed t/11.finfo.t to always join all threads in the thread-safe datetime subtest.
      The previous code used $success &&= $thr->join() which short-circuits as soon as
      any thread returns a false value, leaving the remaining threads finished but