Choco Versions Save

As part of this release we had 1 issue closed.

[!WARNING]

There is a bug in Chocolatey CLI v2.2.0 that prevents upgrading if you have a package dependency that only has pre-release versions (or if the package is no longer available on the sources that you have available). If you receive the error Object reference not set to an instance of an object please uninstall the package that only has pre-release versions available (or which no longer exists on the sources you have available), upgrade Chocolatey CLI, and re-install the package that was uninstalled.

This bug has been fixed in this release of Chocolatey CLI.

[!WARNING]

Refer to our Upgrade Guide for recommendations before upgrading from 1.x versions to 2.x.

Bug Fix

• Fix - Unable to upgrade a package if a dependency only contains pre-release package versions, or if package no longer exists on available sources - see #3292.

[!WARNING]

Chocolatey CLI 2.2.1 was removed from public availability due to a bug identified just prior to the release.

[!WARNING]

Refer to our Upgrade Guide for recommendations before upgrading from 1.x versions to 2.x.

As part of this release we had 3 issues closed.

Bug Fixes

• Fix - Can't find choco.exe after upgrading Chocolatey with MSI - see #3286.
• Fix - Unable to do non-elevated operations when cache location is set to restricted directory - see #3291.

Dependency Change

• Update bundled 7zip executables to v23.01 - see #3285.

[!WARNING]

Refer to our Upgrade Guide for recommendations before upgrading from 1.x versions to 2.x.

As part of this release we had 10 issues closed.

Bug Fixes

• Fix - Upgrading from Chocolatey CLI v2.0.0 to v2.1.0 take a long time to complete when certain other packages are installed - see #3237.
• Fix - Chocolatey CLI v2.0.0 prompts for credentials when authenticating to a source that is using Windows Authentication - see #3242.
• Fix - Chocolatey CLI is unable to save HTTP Cache files when running as a non-admin user and the cacheLocation is set to point at the Chocolatey ProgramData folder - see #3264.

Improvements

• Remove warning message about "smarter than the average bear" - see #3186.
• Improve overall execution time when performing the choco upgrade all command - see #3231.
• Expand logging around the exception that is thrown when Chocolatey CLI is unable to communicate with a source - see #3258.
• Ensure that only Administrators are able to modify files that are stored within the ChocolateyHttpCache folder - see #3281.

Documentation

• Apply scripting best practices to output which is shown from some Chocolatey CLI validations - see #3238.
• Improve error message that is shown when defaultPushSource configuration value hasn't been set and no explicit source has been provided - see #3280.

[!WARNING]

Refer to our Upgrade Guide for recommendations before upgrading from 1.x versions to 2.x.

As part of this release we had 17 issues closed.

Bug Fixes

• Fix - Warning about threshold not shown for multiple sources - see #3190.
• Fix - System proxy settings (automatically detect settings) are no longer used in v2.0.0 - see #3181.
• Fix - Incorrect implementation of the RuleIdEqualityComparer.Equals method - see #3182.
• Fix - choco pin remove -n packagename removes pin for a different package - see #3196.
• Fix - Package version normalization is not being applied everywhere - see #3174.
• Fix - Chocolatey CLI tries to load the licensed environment settings when the licensed extension assembly is not supposed to be loaded - see #3224.
• Fix - Initial chocolatey.config configuration file is initialized with empty descriptions - see #3201.
• Fix - Chocolatey CLI does not use the cachelocation which is configured within the chocolatey.config file - see #3225.
• Fix - Checking for presence of Chocolatey license file in tab expansion PowerShell script generates $error - see #3218.

Improvements

• Create PowerShell helper function to read config values - see #2854.
• Add command to allow purging of cached HTTP queries - see #3194.
• Provide option for Chocolatey CLI commands to skip cached query results - see #3193.
• Degraded performance after upgrading to version Chocolatey CLI v2.0.0 - see #3183.
• choco search command does not use previously cached results - see #3125.

Documentation

• Update contributing documentation to be clearer for newcomers - see #3108.

[!WARNING]

This is a pre-release version of Chocolatey CLI and it is NOT suitable for production use! A pre-release version will have bugs that could have a detrimental impact to your environment. Ensure all necessary due diligence steps are taken before using in your environment.

[!WARNING]

This pre-release version of Chocolatey CLI only works with the alpha version of the Chocolatey Licensed Extension.

[!NOTE]

The issue that was introduced in the previous alpha release regarding the open ended search query has been addressed in this alpha release.

[!NOTE]

Before installing this prerelease version, we would recommend that you read through the Upgrade Instructions for moving to the major version of Chocolatey CLI.

Bug Fixes

• Fix - Warning about threshold not shown for multiple sources - see #3190.
• Fix - System proxy settings (automatically detect settings) are no longer used in v2.0.0 - see #3181.
• Fix - Incorrect implementation of the RuleIdEqualityComparer.Equals method - see #3182.

Documentation

• Update contributing documentation to be clearer for newcomers - see #3108.

[!WARNING]

This is a pre-release version of Chocolatey CLI and it is NOT suitable for production use! A pre-release version will have bugs that could have a detrimental impact to your environment. Ensure all necessary due diligence steps are taken before using in your environment.

[!WARNING]

This pre-release version of Chocolatey CLI only works with the alpha version of the Chocolatey Licensed Extension.

Known Issues

There is a known issue when attempting to do an open ended search query where the Chocolatey Licensed feed is in place. For example, if you run the command choco search --source chocolatey.licensed you will get the following error message returned:

The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

A fix has been found for this problem, and will be released in a future alpha release.

Bug Fixes

• Fix - choco pin remove -n packagename removes pin for a different package - see #3196.
• Fix - Package version normalization is not being applied everywhere - see #3174.

Improvements

• Performance degradation after upgrading to version Chocolatey CLI v2.0.0 - see #3183.
• choco search command does not use previously cached results - see #3125.

[!WARNING]

Refer to our Upgrade Guide for recommendations before upgrading from 1.x versions to 2.x.

As part of this release we had 52 issues closed.

Breaking Changes

• Change default behavior of choco list to be local only - see #158.
• Prevent usage of leading 0 in package version numbers - see #1174.
• choco config list --limit-output does not limit output as expected - see #2013.
• Remove Get-BinRoot Chocolatey helper function - see #2623.
• Remove the default push location when uploading/pushing packages - see #2629.
• Remove deprecated configurations from Config - see #2630.
• Remove deprecated Chocolatey shims (chocolatey, cinst, clist, cpush, cuninst, cup) - see #2642.
• Upgrade to target version 4.8 of the .NET Framework - see #2738.
• Fix spelling mistake in the extract_binary_file_from_assembly function - see #2776.
• Remove side-by-side installs - see #2788.
• Migrate from Rx-* packages to System.Reactive.* packages - see #2896.
• Switch to use only the recommended TLS versions without fallback to earlier insecure options - see #2902.
• Rename or migrate away from custom HashCode class - see #2909.
• Remove WebPI alternative source - see #2980.
• Remove the --remove option in apikey command and replace with remove subcommand - see #2984.
• choco config list should only include information about config - see #2986.
• Disallow passing in a path to a NUPKG file directly when installing/upgrading packages - see #3008.
• Introduce upper limit when querying for packages and warn when threshold is close to being hit - see #3014.

Bug Fixes

• NuGet does not deal with blocking version conflicts from existing installed packages - see #116.
• NuGet doesn't handle conflicts of versions in an install request when HighestVersion dependency - see #507.
• Push command does not honor proxy settings - see #1271.
• Filenames that contain apostrophes aren't handled correctly when calculating checksums - see #1590.
• Chocolatey CLI does not override NuGet proxy with its own - see #1720.
• choco pack command fails with error on Linux when using file greater than 2 GB - see #2278.
• choco info command with no package id defined returns 0 packages found rather than provide a warning - see #2899.

Documentation

• Fix broken URLs in repository README file - see #2888.
• Update Minimum Windows Server OS to Server 2008 R2 - see #2903.
• Update package files to reflect current CCR moderation requirements - see #2920.
• Fix typos and spelling errors - see #2990.

Improvements

• Ability to specify a default source when doing choco push - see #62.
• Upgrade to target version 3.1.0 of Chocolatey.NuGet.Client assemblies - see #508.
• Support Semantic Versioning 2.0.0 (semver) - see #1610.
• choco info command doesn't show package URL - see #1728.
• Ensure that the client version used when querying a repository is the version of the underlying NuGet.Client library - see #1935.
• Alphabetically sort the output from the feature config source and apikey list command - see #2814.
• Add ability to get status of an individual feature (choco feature get) - see #2815.
• Provide ability to navigate directly to online version of help documentation for a command - see #2867.
• PowerShell tab completion should only show commands/options for currently installed license - see #2887.
• Adjust visibility / remove non-interface public methods on CygwinService - see #3028.
• MSI Build should be present in this repository - see #3061.
• Chocolatey products should no longer warn about possible errors when upgrading from versions before 1.0.0 - see #3097.
• Sort list of installed/upgraded packages - see #3112.

As part of this release we had 2 issues closed.

Bug Fix

• Fix - When no hook scripts and installed you cannot install/upgrade a package on a system using PowerShell 2 - see #3088.

Improvement

• Ensure the most recent version of Chocolatey-NuGet.Core package is being used - see #3150.

[!WARNING]

This is a pre-release version of Chocolatey CLI and it is NOT suitable for production use! A pre-release version will have bugs that could have a detrimental impact to your environment. Ensure all necessary due diligence steps are taken before using in your environment.

[!WARNING]

This pre-release version of Chocolatey CLI only works with the beta version of the Chocolatey Licensed Extension.

[!NOTE]

If you run into any problems when using this beta version of Chocolatey CLI we would ask that you comment on this discussion, which is where we will be collating issues, and providing workarounds, etc. We will not be accepting issues raised against this beta release.

Known Issues

See this list for known issues with this pre-release.

Breaking Change

• Switch to use only the recommended TLS versions without fallback to earlier insecure options - see #2902.

Bug Fixes

• Fix - choco info command with no package id defined returns 0 packages found rather than provide a warning - see #2899.
• Fix - Chocolatey CLI does not override NuGet proxy with its own - see #1720.
• Fix - Ensure that correct count query is used when querying oData feeds.

Enhancements

• PowerShell tab completion should only show commands/options for currently installed license - see #2887.
• Alphabetically sort the output from the feature config source and apikey list command - see #2814.
• Add explicit handling for choco list -li to provide backwards compatibility - related to #158.
• Add ability to get status of an individual feature (choco feature get) - see #2815.
• Ensure that the client version used when querying a repository is the version of the underlying NuGet.Client library - see #1935.

[!WARNING]

This is a pre-release version of Chocolatey CLI and it is NOT suitable for production use! A pre-release version will have bugs that could have a detrimental impact to your environment. Ensure all necessary due diligence steps are taken before using in your environment.

[!WARNING]

This pre-release version of Chocolatey CLI only works with the beta version of the Chocolatey Licensed Extension.

[!NOTE]

If you run into any problems when using this beta version of Chocolatey CLI we would ask that you comment on this discussion, which is where we will be collating issues, and providing workarounds, etc. We will not be accepting issues raised against this beta release.

Known Issues

See this list for known issues with this pre-release.

Bugs

• Chocolatey does not override NuGet proxy with its own - see #1720.
• When no hook scripts are installed you cannot install/upgrade a package on a system using PowerShell 2 - see #3088.
• Prevent install/upgrade failure when using multiple sources and one or more of them cannot be reached.

Enhancements

• Chocolatey products should no longer warn about possible errors when upgrading from versions before 1.0.0 - see #3097.
• All the different ways that a proxy can be configured (environment variables, chocolatey.config file, command arguments) have been tested and verified to work as expected.