You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are some configuration management tools that need to check the version of Chocolatey prior to allowing it to set features. This presents an issue when attempting to set FIPS compliance, because any call to choco that isn't enabling the FIPS compliance checksum feature will fail. This should allow a call to find out the version or the default help without error.
The text was updated successfully, but these errors were encountered:
There are some configuration management tools that need to check the
version of Chocolatey prior to allowing it to set features. This
presents an issue when attempting to set FIPS compliance, because any
call to choco that isn't enabling the FIPS compliance checksum feature
will fail. This should allow a call to find out the version or the
default help without error.
* stable:
(GH-1193) Allow version check with FIPS
(GH-1155) do not warn nupkg on pack/push
(GH-1187) File64 - Install-ChocolateyInstallPackage
(maint) Add 64-bit process Information variable
(GH-1155) Warn when .nupkg/.nuspec used in args
(GH-262) BypassProxy on IHttpClient
(GH-1134) use console adapter for width
(GH-1182) trace network traffic
(GH-1181) Configure a source for self-service
(GH-1180) Create .ignore file only in choco path
(GH-1177) Fix: MSU fails when spaces in path
(maint) formatting
(GH-1178) Fix: OS_NAME not reported as Windows 10
(GH-1134) ensure GetPackageManager w/older licensed
(GH-1165) pass proxy bypass list to debug message
There are some configuration management tools that need to check the version of Chocolatey prior to allowing it to set features. This presents an issue when attempting to set FIPS compliance, because any call to choco that isn't enabling the FIPS compliance checksum feature will fail. This should allow a call to find out the version or the default help without error.
The text was updated successfully, but these errors were encountered: