You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we release nuget packages for the compiler with a new build task that task may not be loaded because the task with the same assembly version may have already been loaded with a different path.
If we Rev the minor version every day (by including the date in the version number) then installing various versions of the compiler should be fine as long s they weren't built in the exact same day.
The text was updated successfully, but these errors were encountered:
+1 on just increment the minor version following the semver convention. Doesn't matter if we end up having 4.20.5008, it is still a valid plain semantic version.
When we release nuget packages for the compiler with a new build task that task may not be loaded because the task with the same assembly version may have already been loaded with a different path.
If we Rev the minor version every day (by including the date in the version number) then installing various versions of the compiler should be fine as long s they weren't built in the exact same day.
The text was updated successfully, but these errors were encountered: