-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Update NuGet packages to fill out all metadata. #115
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
Changes from 3 commits
f257d2a
5781cbd
5ca8f81
761c86d
4761f25
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,6 +7,15 @@ | |
<IncludeSymbols>false</IncludeSymbols> | ||
</PropertyGroup> | ||
|
||
<!-- nuspec properties --> | ||
<PropertyGroup> | ||
<Authors>Microsoft</Authors> | ||
<PackageLicenseUrl>https://github.com/dotnet/machinelearning/blob/master/LICENSE</PackageLicenseUrl> | ||
<PackageProjectUrl>https://dot.net/ml</PackageProjectUrl> | ||
<PackageIconUrl>https://aka.ms/mlnetlogo</PackageIconUrl> | ||
<PackageReleaseNotes>https://github.com/dotnet/machinelearning/tree/master/Documentation/release-notes</PackageReleaseNotes> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I have 2 suggested solutions to the package release notes problem listed here: https://github.com/dotnet/corefx/issues/29314#issuecomment-387898104 I am taking the first approach for now (pointing to the root of the release-notes folder). If we agree on the templating approach, we can change it. |
||
</PropertyGroup> | ||
|
||
<!-- Work around https://github.com/NuGet/Home/issues/6091 --> | ||
<ItemDefinitionGroup> | ||
<PackageReference> | ||
|
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.
Just curious, does anything here in the nuspec make it clear to consumers of the nuget not only what repository it comes from, but what the commithash was on build? Not sure if that's buried somewhere in here, if it was it wasn't obvious.
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.
There is a new NuGet feature with the
2.1.200
SDK that just got merged that will put the commit hash and repo in the nuspec file.I'll update this PR to set these properties as well.
See these random collection of links about this:
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.
Very nice, thanks @eerhardt .