4.0.1

What's Changed

• [BREAKING] TimeRange month translation now includes the year, but year is omitted when useRelative is true and anchor.year is same as the range year
• Added Moment.minValueUtc and Moment.maxValueUtc
• Fixed Moment.minValue and Moment.maxValue overflowing
• Updated docs

Full Changelog: 3.1.0...4.0.1

3.3.1

What's new

• Fixed MonthTimeRange.format() would return "This month" for different year's same month

Full Changelog: 3.3.0...3.3.1

3.3.0

What's new

• Pageable TImeRange's next, last no longer generated invalid value (e.g., month 12, day 32, etc..)

Full Changelog: 3.2.1...3.3.0

3.2.1

Full Changelog: 3.2.0...3.2.1

3.2.0

What's Changed

• Turkish locale #28 by @sadespresso in #30

Full Changelog: 2.2.0...3.2.0

3.1.0

What's Changed

• TimeRange now has a unit property that returns its corresponding
  DurationUnit type if available.

Full Changelog: 3.0.0...3.1.0

3.0.0

What's Changed

This release has breaking changes!

• Changed TimeRange.toString() delimiter to @
• Fixed CustomTimeRange not being able to be parsed
• Added .encode() and .encodeShort() methods on TimeRange
• Added TimeRange.fromStartAndDuration constructor

Full Changelog: 2.1.0...3.0.0

2.2.1+beta.0

What's Changed

• TimeRange readable format beta. Call .format() on TimeRange objects.

Absolutely not tested :D

Full Changelog: 2.2.0...2.2.1+beta.0

2.2.0

What's Changed

• fix #19, .endOf(DurationUnit.week) was incorrectly returning 7 days ahead by @sadespresso in #20
• Renamed DateTime.to to .rangeTo for clarity. Old method will be removed on the next
• Added Moment.maxValue and Moment.minValue. For example, now you can use CustomTimeRange(now, Moment.maxValue) or epoch.to(Moment.maxValue)

Full Changelog: 2.1.0...2.2.0

2.1.0

What's changed

• Fixed LocalWeekTimeRange and IsoWeekTimeRange's to being 1 microsecond ahead
• Now you can parse/serialize TimeRange by calling TimeRange.parse() and TimeRange.toString()