Release 7.0.0

🔨 Fixes

• Fixed an issue where certain nullable dates weren't treated as nullable, and thus were converted anyways (resulting in a Date with a timestamp of 0) (Fixes #7)

This is technically a breaking change for a couple reasons:

• While the field is marked as nullable (aka potentially falsey), this was always returning something truthy, and anyone relying on this behavior will have their code broken
• Related to the above: anyone not checking if the property is truthy may run into issues when trying to treat the object as a Date (as now it may be null)