Resolved Semantic versioning parsing failure when I build player content?

I am getting this log error message and I can't figure out why. It seemed to happen after I updated to a new version of a GitHub based dependency, but why is Addressables trying to parse version numbers? Is this something that could be fixed on the Addressables side? This is the first time I've seen this error and not sure what information I can provide for the dependency to prevent this from happening. Tried updating to the latest Addressables preview but I get the same error message

Code (CSharp):

1.  
2.  ArgumentException: Not Found
3. UnityEditor.Scripting.ScriptCompilation.SemVersionRanges.GetExpression (System.String expression) (at /Users/bokken/buildslave/unity/build/Editor/Mono/Scripting/ScriptCompilation/SemVersionRanges.cs:35)
4. UnityEditor.Scripting.ScriptCompilation.SemVersionRangesFactory.GetExpression (System.String expression) (at /Users/bokken/buildslave/unity/build/Editor/Mono/Scripting/ScriptCompilation/SemVersionRangesFactory.cs:16)
5. UnityEditor.Scripting.ScriptCompilation.EditorCompilation.GetTargetAssemblyDefines (UnityEditor.Scripting.ScriptCompilation.TargetAssembly targetAssembly, UnityEditor.Scripting.ScriptCompilation.SemVersionRangesFactory semVersionRangesFactory, System.Collections.Generic.Dictionary`2[TKey,TValue] assetPathVersionMetaDatas, System.String[] editorOnlyCompatibleDefines, System.String[] playerAssembliesDefines, UnityEditor.Scripting.ScriptCompilation.ScriptAssemblySettings settings) (at /Users/bokken/buildslave/unity/build/Editor/Mono/Scripting/ScriptCompilation/EditorCompilation.cs:2527)
6. UnityEditor.AddressableAssets.Settings.AddressableAssetSettings:BuildPlayerContent()

 

Okay I figured out the cause of this problem. The dependency declared a version define without giving a valid version range which caused this error to come out in tons of places. So the dependency had to fix their version define in their asmdef from "1" to something like "[1.0, 2.0)"

 

Also: the inspector for asmdefs still sucks donkey - with no red text, no console errors, nothing - it (almost silently) says 'invalid' for a version like '1', and then generates this non-sensical error on console later. Sigh.