All Versions
29
Latest Version
Avg Release Cycle
55 days
Latest Release
339 days ago

Changelog History
Page 1

  • v3.6.1

    June 27, 2019

    Potentially Breaking

    • Require Elixir v1.6+

    ➕ Added

    • ✅ Setup property based test framework and add sample tests (#480)
    • 🌐 Turkish translation (#534)
    • ➕ Add details to parsing documentation (#540)
    • 👌 Support time units in singular (#509)
    • 📚 #538 documentation of default formatting directives
    • 👌 Support for tzdata 1.0.0 (#536)

    🛠 Fixed

    • ➕ Address handling of ambiguity in timezone conversions by using UTC clock time, where possible. See #488
    • #491 gracefully handle errors resolving a timezone using wall clock time
    • #514 gracefully handle converting date to datetime on tz boundary
    • #531 address some issues with shifting over timezone boundaries
    • #507 unnecessary tz conversion during logical shifts results in erroneous results
    • #532 shift priority incorrectly inverted
    • #537 precision not preserved in some situations
    • 🗄 Elixir 1.8 deprecations
    • Timex.diff/2 spec
    • Timex.Timezone.convert/2 when using custom time zones
    • 🌐 Letter encoding on PT translation
    • 🌐 Swedish translation id for March
  • v3.6.0

    June 26, 2019
  • v3.5.0

    January 18, 2019

    ➕ Added

    • Timex.set/2 now also accepts setting the :date from a %Date{} struct.
    • 🚚 Interval.difference/2 removes one interval from another
  • v3.4.2

    November 03, 2018
  • v3.4.1

    September 19, 2018

    ➕ Added

    • 🌐 Afrikaans translations (Julian Dicks)
    • The :inclusive option for Timex.between?/4 :start and :end in addition to true

    🛠 Fixed

    • strftime_iso_kitchen no longer discards dates
  • v3.4.0

    July 12, 2018

    NOTE: There are breaking changes in this release. This is not going to result in a major 🔖 version bump, as the old behavior did not match the docs, and was incorrect to boot. In other words, the 💥 breaking changes only affect you if you relied on the incorrect behavior, if you were expecting the documented behavior, then these are not breaking changes.

    ➕ Added

    • ✅ Interval.contains?/2 to test if one interval contains another

    🛠 Fixed

    • Interval overlap was being improperly calculated
    • Interval behavior with respect to open/closed bounds was incorrect (open bounds were being treated as closed and vice versa)
    • Intervals could be created with invalid from/until (i.e. creating an interval with an until before the from)
    • 📚 Interval documentation improvements for clarity
  • v3.3.0

    May 08, 2018
  • v3.2.2

    April 14, 2018
  • v3.2.1

    February 20, 2018
  • v3.2.0

    February 20, 2018