-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(#770) Clarify Package Environment variables and their contents #764
Conversation
a335219
to
cc60de0
Compare
cc60de0
to
487c9b4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple things, but otherwise this looks good :3
3fcfd3a
to
c12a720
Compare
0568b5a
to
aaef978
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good work @corbob. Thanks for persevering.
In order to get this one over the line, I am going to get it rebased to fix up the merge conflict, and then get it merged. This is based on the fact that @pauby has already approved it. |
If Package Maintainers use the ChocolateyPackageVersion environment variable, and the version number is not normalized, then this could lead to undesired package results. This commit adds a note to the upgrade guide regarding this and cautioning package maintainers from using this.
Update the Environment Variable information to note that ChocolateyPackageName is lower case, and that ChocolateyPackageVersion is normalized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Description Of Changes
Add a note to the upgrade guide for Package Maintainers to be aware that the ChocolateyPackageVersion is normalized in Chocolatey CLI Version 2.0.0. Add some clarifying words around the ChocolateyPackageName variable that it is a lower case version of the id.
Motivation and Context
The normalization of Version numbers could behave differently depending on the package scripts. There used to be at least one package that expected ChocolateyPackageName to exactly match the nuspec file and it didn't work when the casing was changed.
Testing
Change Types Made
Change Checklist
Related Issue
$env:ChocolateyPackageVersion
in packages #770