All notable changes to the Unity3D NuGet package will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Internal: this changelog!
- Package icon to use new Unity logo
UnityVersionMajor
,UnityVersionMinor
,UnityVersionPatch
, andUnityVersionAsNumber
props for manipulation of Unity versions as numbers- Documentation on using the numeric Unity version properties in MSBuild files
- Support documentation to main README
- Internal: test projects for Tech Stream Unity releases up through 2022.1
- Updated usage notes in all Readme documents
- Updated available short-hand properties in all Readme documents
OSInstallRoot
toOSInstallRootPath
andUnityInstallRoot
toUnityInstallRootPath
, to be consistent with other prop names- Assembly short-hand properties now defined conditionally based on
UnityVersion
- Many new short-hand properties, with more consistent naming (relative paths end in
Dir
orAssembly
, absolute paths end inPath
)
- Unity version can now be parsed automatically from the
ProjectVersion.txt
file in a Unity project, if not set explicitly (requiresUnityProjectPath
to be set) - Reference Include paths no longer need to start with
$(UnityInstallRoot)\$(UnityVersion)
. Most paths will now use a single short-hand property. - If neither
UnityVersion
norUnityProjectPath
is explicitly set, thenUnityVersion
is set to a constant string to explain the issue. UnityVersion
orUnityProjectPath
must be set in aDirectory.Build.props
, not the project file.- ASCII art in package readme.txt to use new Unity logo
- Root paths for Linux
- Suggested
TargetFramework
notes in main README - Internal: tests for Unity 2020.2.x
- Contributor Covenant to v2.0
- Clarified Unity versions that we officially support in main README
- Root paths for MacOS (thanks to input from GitHub user Sorrowful-free)
- Short-hand properties for iOS- and Android-specific assemblies
- Short-hand property for Newtonsoft.Json
- Internal: test projects for Unity 2019.4.x and 2020.1.x
- Documentation about which Unity packages are necessary for which MSBuild short-hand properties
- Internal: test projects for Unity 2019.3.x
- Some property conditions in the main
.props
file
- Short-hand properties for more locations, including assemblies within a Unity project folder
- Internal: some test Unity scenes in various Unity versions, for testing builds that reference Library/ or Asset Store assemblies
- README instructions on removing the default
UnityEngine.dll
reference - README instructions on referencing assemblies in Packages, Asset Store assets, and Unity modules
- Internal: test solution is now more flexible, containing fewer projects that can each be built with a different target framework and version of Unity
- Main README's usage section now better organized into sub-sections
- Unnecessary
UNITY_ASSERTIONS
define
- Missing
UnityModulesPath
property 🤦
- All short-hand assembly properties now use the same casing as the referenced DLL files (e.g.,
UnityEngineUIPath
, notUnityEngineUiPath
)
- New
UnityManagedPath
andUnityExtensionsPath
properties to clean up the props file
First stable release.
Final preparations for first stable version.
References are now added as Reference
items, not magic MSBuild properties.
Initial package release.