Closed YixiongJiang closed 3 years ago
thanks @YixiongJiang good find. I'll check it out. cheers
@spencermountain Thanks, for your more information, I found there is a workaround to avoid this bug: date.add(30*12, 'month'), will get correct result: "2030-01-01 00:00:00"
yikes! will add this to the next release, ideally next week. thank you
fixed in v6.16.3
- thank you!
Expected: "2030-01-01 00:00:00" Received: "2029-01-01 00:00:00"
It happens when unit is year and when the value is a multiple of 5.
Just curiosity, why not just add value to the year numerically?