Is your feature request related to a problem? Please describe.
There is a bit of kludginess to the current release process where nuget and unity releases are done separately. This was done intentionally, but on testing the v2 integration to ER there are dependencies between the Unity integration and Nuget package which can make it difficult and potentially cause errors/issues on differences between the assemblies provided in the either release.
Describe the solution you'd like
I'd like for the release process to be more streamlined overall (fewer steps) and for a minimum to no build artifacts to be checked in to the develop branch as a part of the release build process. Ideally:
All unit tests for both the Unity and nuget package should be done before releases are pushed.
Is your feature request related to a problem? Please describe. There is a bit of kludginess to the current release process where nuget and unity releases are done separately. This was done intentionally, but on testing the v2 integration to ER there are dependencies between the Unity integration and Nuget package which can make it difficult and potentially cause errors/issues on differences between the assemblies provided in the either release.
The current process is documented here.
Describe the solution you'd like I'd like for the release process to be more streamlined overall (fewer steps) and for a minimum to no build artifacts to be checked in to the develop branch as a part of the release build process. Ideally: