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
With checksums, each different checksum will have a certain number of characters. It would be nice if we could automatically determine that value and adjust in case the package doesn't specify or specifies it incorrectly.
The text was updated successfully, but these errors were encountered:
Upgrade checksum to v0.1.0 to take advantage of auto checksum
detection. When passing a checksum, the checksum type will
automatically be determined by the length of the checksum that is being
passed for verification.
* stable: (24 commits)
(GH-839) Switch to apply package parameters to dependent packages
(maint) formatting methods / parameters in calls
(GH-958) If SSLv3 in Posh v2 Fails, Use Original
(GH-746) Use HTTPS if available when HTTP url
(GH-957) Skip Get-WebFileName When FTP
(GH-948) Ensure passwords / keys are not logged
(GH-952) Get-ChocolateyWebFile enhancements
(doc) update generated docs
(maint) formatting
(docs) move GenerateDocs.ps1 / update
(GH-932) Do not set unknown checksum to 'md5'
(GH-719) Reset ServerCertificateValidationCallback
(GH-305) add MSP/MSU installer types
(GH-305) update exitcodes to long
(GH-954) Pending fails when lib does not exist
(GH-950) Install-ChocolateyPackage - UseOriginalLocation
(maint) formatting
(GH-922) Automatically determine checksum type
(maint) fixes for shimgen
(GH-948) Do not log sensitive arguments
...
With checksums, each different checksum will have a certain number of characters. It would be nice if we could automatically determine that value and adjust in case the package doesn't specify or specifies it incorrectly.
The text was updated successfully, but these errors were encountered: