Releases: GlitchEnzo/NuGetForUnity
Releases · GlitchEnzo/NuGetForUnity
1.0.4
1.0.3
v1.0.2
v1.0.1
- Fix cases where package would be found in one source then overwritten by a lower version found on a different source.
v1.0.0
- Several teams/companies have been using NuGetForUnity successfully, so we're calling this a 1.0 release.
- Package install considered a failure if dependencies fail to install.
- Fix DirectoryNotFoundException in clean project.
- Fix packages removed from .config still show as installed.
- Add MacOS support.
v0.0.18
- Add project and repo info to Nuget Window (makes it easy to find the project or clone the source code associated with a package)
- Previously-installed packages are deleted if they have been removed from packages.config. (Previously, if you pulled someone else's change from Git that removed a package then the package would remain in your nuget Packages folder.)
- Cache icons in Application.temporaryCachePath folder
- Support nuspec dependancies with the "group" xml element
v0.0.17
- Upgrade to Unity version 5.3.0f4
- VSTS nuget feed credential provider
- Build script for packaing up project
- Fix for missing default icon
- Fix for missing LICENSE
v0.0.16
- .NET Standard 2.0 support
- Include Content folder.
- Security fix: update DotNetZip.dll to version 1.11.0.0
v0.0.15
- Package files are now set to read-only in order to prevent users from inadvertently editing them. Typically, package files are placed in .gitignore so they are not checked in and should not be changed. If this new behavior is not desired, it can be disabled in Preferences > NuGetForUnity > Read-Only Package Files.
Bug Fixes:
- Fixed Unity 5.2 incompatibility.
- Fixed case-sensitive comparison reading NuGet.config file.
v0.0.14
- Check for Updates feature to update NuGetForUnity itself
Bug fixes:
- Fixed GetUpdates() error with Visual Studio Team Services package feed
- Fixed NullReferenceException when updating a package
- Fixed duplicate packages in package.config due to case sensitivity