The IANA time zone database published an update a couple days ago, and yesterday I uploaded the changes to a few of my web applications. Then one of the applications blew up. This is because I hadn't accounted for the possibility that a time zone abbreviation could include non-alpha-numeric characters.
Within an hour I'd updated the affected code and published an updated NuGet package. So now it's fixed. I just have to update a couple of applications that have all their time zone data in caches, so that when they reload the data, they continue functioning. (This blog is one of the apps.)
Meanwhile, you can see the problem if you go to the Inner Drive time zone demo, select Europe/Astrakhan, you'll see the "+03" or "+04" that my stuff couldn't parse properly.
So one of my customers, not quite understanding how NuGet works, asked about what they should do if they need something in an Inner Drive package changed. Let this be an example of why they might not need even to ask. And also, contrast this quick response with, say, Microsoft, who created most of the packages that people use in ASP.NET applications.