Releases: devlooped/nugetizer
Releases · devlooped/nugetizer
v0.9.1
v0.9.0
Changelog
v0.9.0 (2022-09-03)
✨ Implemented enhancements:
- Allow including content in the package readme from a URL #216
- Support markdown includes in package readme files #210
- Support transitive package dependency from P2P #202 (@kzu)
🐛 Fixed bugs:
- If readme isn't already a @(None) item, it's not automatically added to package #213
- Support transitive package dependency of referenced (non-packing) project #199
- Packaging when using Nerdbank.Gitversioning fails #198
- Yellow triangle on Nugetizer nuget package reference under project dependencies -> packages #196
- running nugetize fails - unable to find framework #189
🔀 Merged:
v0.8.0
v0.8.0-beta
Fix nuget publish path
v0.7.6
Changelog
v0.7.6 (2022-05-26)
🐛 Fixed bugs:
- Packing with Microsoft.Build.NoTargets doesn't put dependency under proper target framework group when reference other Microsoft.Build.NoTargets project #155
- Cannot use PackageRequireLicenseAcceptance = true with Microsoft.Build.NoTargets sdk #149
- Do BuildAction and CopyToOutput work? #143
🔀 Merged:
- Bump test dependencies #177 (@kzu)
- Allow specifying that packaging projects are framework specific #176 (@kzu)
- Fix contentFiles relative path in manifest #175 (@kzu)
- A few fixes for cleanup targets #166 (@gpwen)
- Fixed a few typos in the readme #161 (@AntonC9018)
New Contributors
- @AntonC9018 made their first contribution in #161
- @gpwen made their first contribution in #166
v0.7.5
v0.7.5 (2021-10-13)
✨ Implemented enhancements:
- Normalize all paths for consistency, use SDK Pack format #135
- PackAsTool from SDK Pack should cause PackFolder=tool #131
🐛 Fixed bugs:
- SDK Pack always packs tools as framework-specific #132
- dotnet.exe nugetize My.sln errors if one project doesn't PackageReference Nugetizer #107
- Fixes using of license file. #150 (@denjmpr)
🔀 Merged: