v7.1.2

What's Changed

• Fix flag at beginning of METAR message not being handled (#50) by @aeharding in #51

Full Changelog: v7.1.1...v7.1.2

v7.1.1

What's Changed

• Add hardened weather condition parsing by @aeharding in #32
• Fix VCBLSN not being parsed as a weather condition by @aeharding in #49

Full Changelog: v7.1.0...v7.1.1

v7.1.0

What's Changed

• Fix CAVOK propagating BECMG upon encountering conflicting conditions by @aeharding in #38
• Properly parse wind conditions with turbulence group by @aeharding in #33
• Remove unused models (Airport, Country) by @aeharding in #40
• secondaryType on ICloud by @aeharding in #37
• Fix parsing for unknown cloud type (///) by @aeharding in #36
• Improve malformed cloud string parsing, error handling for command execution by @aeharding in #41
• Add flight category, ceiling information to README.md by @aeharding in #42
• Add icing and turbulence support to TAF reports by @aeharding in #39
• Add unknown cloud height parsing by @aeharding in #44
• Fix incorrect start validity date when it's the day before issued date by @aeharding in #45

Full Changelog: v7.0.0...v7.1.0

v7.0.0

What's Changed

• Add INTER support by @aeharding in #35
• Upgrade example website, fix misc, renaming by @aeharding in #34

Breaking changes

Pretty minimal!

1. You may need to add additional logic to your app to handle the newly parsed INTER (intermittent) TAF trend type.
2. For those using the getCompositeForecastForDate API:
   a. base has been renamed to prevailing
   b. additional has been renamed to supplemental

Full Changelog: v6.1.4...v7.0.0

v6.1.4

What's Changed

• Fix raw property for metar trends by @aeharding in #31

Full Changelog: v6.1.3...v6.1.4

v6.1.3

What's Changed

• Add no significant weather as a weather condition by @aeharding in #30

Full Changelog: v6.1.2...v6.1.3

v6.1.2

What's Changed

• Add NSW weather flag to trends, fix BECMG propagating wx when NSW exists by @aeharding in #29

Full Changelog: v6.1.1...v6.1.2

v6.1.1

What's Changed

• Fix raw trend not matching input when using min/max temp on TAF by @aeharding in #28

Full Changelog: v6.1.0...v6.1.1

v6.1.0

What's Changed

• Add SpeedUnit enum by @aeharding in #27

Full Changelog: v6.0.0...v6.1.0

v6.0.0

What's Changed

• Add dated min/max temps, better forecast validity logic by @aeharding in #26

Full Changelog: v5.1.0...v6.0.0

Breaking Changes

Breaking changes are limited to the Forecast abstraction. If you use parseTAF or parseMETAR directly, you can safely upgrade.

Breaking changes related to Forecast API:

1. Each forecast[] object no longer has validity, since it's too low level and has strange caveats depending on the type (FM/BECMG/TEMPO/etc). Instead, start and end are on the base object, and are a higher level: FM and BECMG now have ends determined by the next FM/BECMG, or the end of the report validity. This is much more intuitive when rendering a UI to show the user the decoded TAF, and is similar to what aviationweather.gov does when showing a decoded TAF.
2. BECMG has unchanged conditions propagated from earlier FM/BECMG/initial weather conditions. This allows it to be treated as more of a first-class validity period, like FM.
3. BECMG is now a base condition of getCompositeForecastForDate instead of in additional