Chocolatey v0.9.9.7 Release Notes

Release Date: 2015-06-20 // almost 9 years ago
  • ๐Ÿ“ฆ "Fix Everything. Fix All The Things" - There have been some things bugging us for a long time related to limitations with NuGet, so we decided to fix that. Like nuspec enhancements, that crazy content folder restriction has been removed (I know, right?!), and we're working around badly behaved packages quite a bit more to bring you more feature parity.

    ๐Ÿš€ Let's talk about a couple of big, like really big, BIG features just added with this release. No more packages rebooting Windows. We fixed (#304 / #323) and enhanced up the Auto Uninstaller Service quite a bit to ensure things are working like you would expect (It goes on by default in 0.9.10 - we'll start documenting more about it soon). But wait, there's more! I haven't even told you about the big features yet

    The first big feature is enhancing the nuspec. I mentioned this I know, but now you can use packageSourceUrl in the nuspec to tell folks where you are storing the source for the package! We also added projectSourceUrl, docsUrl, mailingListUrl, and bugTrackerUrl. What's even better is that the community feed has already been enhanced to look for these values. So have the templates from choco new. And it's backwards compatible, meaning you can still install packages that have these added nuspec enhancements without issue (but we will need to provide a fix for Nuget Package Explorer).

    โฌ†๏ธ The second is Xml Document Transformations (XDT), which I think many folks are aware of but may not realize what it can provide. NuGet has allowed transformations for quite awhile to allow you to make changes to an app.config/web.config on install/uninstall. We are following in similar footsteps to allow you to do similar when installing/upgrading packages. We will look for *.install.xdt files in the package (doesn't matter where) and they will apply to configuration files with the same name in the package. This means that during upgrades we won't overwrite configuration files during upgrades that have opted into this feature. It allows you to give users a better experience during upgrades because they won't need to keep making the same changes to the xml config files each time they upgrade your package.

    ๐Ÿ”‹ FEATURES

    • Allow XDT Configuration Transforms - see #331
    • Prevent reboots - see #316
    • Enhance the nuspec - first wave - see #205
    • Uninstaller Service Enhancements - see #305

    ๐Ÿ› BUG FIXES

    • When uninstall fails, do not continue removing files - see #315
    • Do not run autouninstaller if the package result is already a failure - see #323
    • Fix - Auto Uninstaller can fail if chocolateyUninstall.ps1 uninstalls prior to it running - see #304
    • Fix - Packages with content folders cannot have a dependency without also having a content folder - see #290
    • Remove ShimGen director files on upgrade/uninstall - see #326
    • If feature doesn't exist, throw an error - see #317
    • Fix - The operation completed successfully on stderr - see #249
    • Fix - When specific nuget version is needed by a package it is the chocolatey version that is used - see #194
    • When installing with *.nupkg, need to get package name from package, not file name - see #90
    • Fix - Choco pin list is not returning a list - see #302
    • Fix - A pin is not created for existing installations (prior to new choco) - see #60

    ๐Ÿ‘Œ IMPROVEMENTS

    • Allow upgrade to always install missing packages - see #300
    • Enhance Templates - see #296
    • Always log debug output to the log file - see #319
    • Warn when unable to snapshot locked files - see #313
    • Use %systemroot% in place of %windir%. PATH exceed 2048 breaks choco - see #252
    • Add fault tolerance to registry snapshot checks - see #337