@marnusw let's do it when you'll have time, thanks in advanced!

@marnusw thanks for merging! Would you please publish a new version of library to npm?

Ran out of time this morning. I will. 👍🏻

Ran out of time this morning. I will. 👍🏻

Not published yet? https://www.npmjs.com/package/date-fns-tz v3.1.3

v3.2.0

Just to confirm -- this maintains backwards-compatibility with date-fns 3.x?

Just to confirm -- this maintains backwards-compatibility with date-fns 3.x?

No. You should you use previous version v3.1.3

Just to confirm -- this maintains backwards-compatibility with date-fns 3.x?

No. You should you use previous version v3.1.3

Thanks! Probably a good idea to put this in the release notes. And really shouldn't this be v4.0.0 since its a breaking change?

Look at package.json. if support was dropped it would be in the release notes.

I understand what's in package.json. I'm being cautious here and making sure there are no caveats to bite us.

@marnusw so you're saying 3.2.0 does still support date-fns 3.x? And @eshimischi is incorrect?

I understand what's in package.json. I'm being cautious here and making sure there are no caveats to bite us.

@marnusw so you're saying 3.2.0 does still support date-fns 3.x? And @eshimischi is incorrect?

Of course package has no incompatible changes except peer dependency extended to v4.0.0 of date-fns. My bad for making a confusion. You can use v3.2.0 with date-fns v3

Got it, thanks for the clarification.