`--starting-date` not working in 2024

[IllusionVK]

We have been using Auto-chnagelog for the past 1-2 years and all has been working well, however in last few days we have seen issues with the change log being empty when we use our normal command which includes --starting-date.

If we remove --starting-date then the change log shows all changes in the past year or more.

This is an example of the command that is being run (and has worked fine for last 1-2 years) auto-changelog --commit-limit false --starting-date 2024/01/07 --sort-commits date-desc -t conventional -o ReleaseNotes.md

and it is now returning a change log with only

# Change Log
# 

In testing we have found that if we run the command from above but change the date to be 2023 eg 2023/01/07 then it will show the commits only since 1st January of 2024 (thats not a typo... we set 2023 and it shows us commits from 2024)

• We have checked that the clock on our servers are set correctly, which they are (they are synced using NTP)
• We have checked that git is recording the commits correctly as 2024 dates
• We are running the commands on Windows Server 2016 and 2019 and both see the same issues
• If we dont specify a template we see the same issue, so we have ruled that out as a cause
• We have also checked the auto-changelog repo code for when --starting-date was added and didn't see any obvious things of how something like this could happen in the code

@cookpete do you have or anyone else have any the suggestions why this may happen ? Thanks for any ideas on this strange issue!

[IllusionVK]

An Update:

• First we made sure that our tags were annotated and not 'lightweight' git tags. When we did that the problem went away on the Windows 2016 server 🎉 but the problem still occurred on the Windows 2019 Server 🫤
• We compared all settings and made sure that both servers used the same settings/github actions commands and versions
• Finally today we noticed that in the --starting-date command we were passing dates with slashes and not dashes.. when we changed that the problem was solved on the Windows 2019 server 🎉

So the strange thing here is that the 2016 server is still using dates with slashes and it works fine! So there must be something differnt with a library that interprets the date on the Windows 2019 server. We have checked all of our library versions and both servers have the same, so its a mystery what actually causes the issue. Perhaps how regex behaves / how the date is interpreted by the code when run on the 2019 server. To recap:

• Works on 2016 server but NOT on 2019 server --starting-date 2024/01/07
• Works on 2016 server and also on 2019 server --starting-date 2024-01-07